Testing throughout the SDLC Flashcards

1
Q

Formal testing with respect to user needs, requirements, and
business processes conducted to determine whether or not a
system satisfies the acceptance criteria and to
enable the user, customers or other authorized entity to
determine whether or not to accept the system.

A

Acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Simulated or actual operational testing conducted in the developer’s test environment, by roles outside the
development organization.

A

Alpha testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Simulated or actual operational testing conducted at an external site, by roles outside the development organization.

A

Beta Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Provided to ensure that previously eradicated bugs have been fixed and to catch bugs that may have been accidentally appeared into a new version. According to these goals, there are two subtypes of Change related testing: Confirmation testing (Re-testing) and Regression testing.

A

Change-Related Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.

A

Commercial off-the-

shelf (COTS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Testing performed to expose defects in the interfaces and interactions between integrated components.

A

Component integration testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

The testing of individual hardware or software components

A

Component testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Dynamic testing conducted after fixing defects with the objective to confirm that failures caused by those defects do not occur anymore.

A

Confirmation testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Acceptance testing conducted to verify whether a system satisfies its contractual requirements.

A

Contractual acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Testing conducted to evaluate the compliance of a

component or system with functional requirements.

A

Functional Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

The identification of all work products affected by a change, including an estimate of the resources needed to accomplish the change.

A

Impact analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

A

Integration testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Testing the changes to an operational system or the impact of a changed environment to an operational system.

A

Maintenance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Testing conducted to evaluate the compliance of a

component or system with non-functional requirements.

A

Non-Functional Testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on operational aspects, e.g., recoverability, resource-behavior, installability and technical compliance

A

Operational

acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Testing of a previously tested component or system following modification to ensure that defects have not been introduced or have been uncovered in unchanged areas of the software, as a result of the changes made.

A

Regression Testing

17
Q

Acceptance testing conducted to verify whether a system conforms to relevant laws, policies and regulations.

A

Regulatory Acceptance Testing

18
Q

A type of development lifecycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.

A

Sequential development model

19
Q

Testing the combination and interaction of systems.

A

System integration testing

20
Q

Testing an integrated system to verify that it meets specified requirements.

A

System Testing

21
Q

The body of knowledge used as the basis for test analysis and design.

A

Test basis Chapter 1

22
Q

A set of preconditions, inputs, actions (where applicable), expected results and post conditions, developed based on test conditions.

A

Test case Chapter 1

23
Q

An environment containing hardware, instrumentation,
simulators, software tools, and other support elements
needed to conduct a test

A

Test Environment

24
Q

A specific instantiation of a test process

A

Test Level

25
Q

The component or system to be tested.

A

Test object

Chapter 1

26
Q

A reason or purpose for designing and executing a test.

A

Test objective

Chapter 1

27
Q

A group of test activities based on specific test objectives aimed at specific characteristics of a component or system.

A

Test type

28
Q

Acceptance testing conducted in a real or simulated

operational environment by intended users focusing their needs, requirements and business processes.

A

User Acceptance Testing (UAT)

29
Q

Testing to evaluate the degree to which the system can be used by specified users with effectiveness, efficiency and satisfaction in a specified context of use

A

Usability testing

30
Q

A sequential development lifecycle model describing a one-for-one relationship between major phases of software development from business requirements specification to delivery, and corresponding test levels from acceptance testing to component testing

A

V-Model

31
Q

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]

A

Validation

32
Q

Confirmation by examination and through provision of

objective evidence that specified requirements have been fulfilled. [ISO 9000

A

Verification

33
Q

Testing based on an analysis of the internal structure of the component or system.

A

White-Box Testing