Keywords Flashcards

1
Q

Acceptance testing

A

A test level that focuses on determining whether to accept the system.

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

Black-box testing

A

Testing based on an analysis of the specification of the component or system.

specification-based testing

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

Component integration testing

A

The integration testing of components.

module integration testing, unit integration testing

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

Component testing

A

A test level that focuses on individual hardware or software components.

module testing, unit testing

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

Confirmation testing

A

A type of change-related testing performed after fixing a defect to confirm that a failure caused by that defect does not reoccur.

re-testing

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

Functional testing

A

Testing performed to evaluate if a component or system satisfies functional requirements.

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

Integration testing

A

A test level that focuses on interactions between components or systems.

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

Maintenance testing

A

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

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

Non-functional testing

A

Testing performed to evaluate that a component or system complies with non-functional requirements.

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

Regression testing

A

A type of change-related testing to detect whether defects have been introduced or uncovered in unchanged areas of the software.

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

Shift left

A

A test approach to perform testing and quality assurance activities as early as possible in the software development lifecycle.

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

System integration testing

A

The integration testing of systems.

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

System testing

A

A test level that focuses on verifying that a system as a whole meets specified requirements.

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

Test level

A

A specific instantiation of a test process.

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

Test object

A

The work product to be tested.

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

Test type

A

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

17
Q

White-box testing

A

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

clear-box testing, code-based testing, glass-box testing,
logic-coverage testing, logic-driven testing, structural testing,
structure-based testing

18
Q

Sequential development model

A

A type of software 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.

19
Q

V-model

A

A sequential software 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.

20
Q

Iterative development model

A

A type of software development lifecycle model in which the component or system is developed through a series of repeated cycles.

21
Q

Incremental development model

A

A type of software development lifecycle model in which the component or system is developed through a series of increments.

22
Q

Test-driven development

A

A software development technique in which the test cases are developed, automated and then the software is developed incrementally to pass those test cases.

TDD

23
Q

Acceptance test-driven development

A

A collaboration-based test-first approach that defines acceptance tests in the stakeholders’ domain language.

ATDD

24
Q

Behavior-driven development

A

A collaborative approach to development in which the team is focusing on delivering expected behavior of a component or system for the customer, which forms the basis for testing.

BDD

25
Q

Feature-driven development

A

An iterative and incremental software development process driven from a client-valued functionality (feature) perspective. Feature-driven development is mostly used in Agile software development.

26
Q

Continuous integration

A

An automated software development procedure that merges, integrates and tests all changes as soon as they are committed.

27
Q

Stub

A

A type of test double providing predefined responses.

28
Q

user acceptance testing

A

A type of acceptance testing performed to determine if intended users accept the system.

UAT

29
Q

Operational acceptance testing

A

A type of acceptance testing performed to determine if operations and/or systems administration staff can accept a system.

production acceptance testing

30
Q

Regulatory acceptance testing

A

A type of acceptance testing performed to determine the compliance of a test object.

31
Q

Alpha testing

A

A type of acceptance testing performed in the developer’s test environment by roles outside the development organization.

32
Q

Beta testing

A

A type of acceptance testing performed at an external site to the developer’s test environment by roles outside the development organization.