Chapter 1 Vocabulary Flashcards

Vocabulary covered by the ISTQB Foundations 4.0 Exam (46 cards)

1
Q

Actual result

A

Behavior or result produced when something is tested

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

Anomaly

A

A deviation from the expected result

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

Alpha testing

A

An acceptance testing method occurring within the test environment by roles outside the developers organization

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

Agile Software Development

A

Based on Iterative Incremental Development, where requirements and solutions evolve through collaboration between self-organizing functional teams

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

API Testing

A

Performed by submitting requests to the test object through API (application programming interface)

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

Audit

A

Independent examination of a work product or process from third parties to assess compliance with specifications, standards, contractual agreements, or other criteria

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

Availability

A

The degree to which a component or system is operational and accessible when required for use

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

Behavior-driven development

A

The team focuses on expected behavior of the system based on expectations from the customer

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

Acceptance Criteria

A

The criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

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

Acceptance Test-Driven Development (ATDD)

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
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.

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

Black-Box test technique

A

A test technique based on an analysis of the specification of a component or system.

No source code or internals need to be seen for this kind of testing.

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

Boundary Value

A

A minimum or maximum value of an ordered equivalence partition.

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

Boundary Value Analysis

A

A black-box test technique in which test cases are designed based on boundary values.

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

Branch

A

A transfer of control between two consecutive nodes in the control flow graph of a test item.

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

Branch Coverage

A

The coverage of branches in a control flow graph.

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

Branch Testing

A

A white-box test technique in which the test conditions are branches.

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

Coverage

A

The degree to which specified coverage items are exercised by a test suite, expressed as a percentage. Synonyms: test coverage

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

Defect

A

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.
Reference: After ISO 24765
Synonyms: bug, fault

20
Q

Debugging

A

The process of finding, analyzing and removing the causes of failures in a component or system

21
Q

Error

A

A human action that produces an incorrect result.
Reference: ISO 24765
Synonyms: mistake

22
Q

Failure

A

An event in which a component or system does not perform a required function within specified limits.

23
Q

Quality

A

The degree to which a work product satisfies stated and implied needs of its stakeholders.

24
Q

Quality Assurance

A

Activities focused on providing confidence that quality requirements will be fulfilled.

25
Root Cause
A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.
26
Test Analysis
The activity that identifies test conditions by analyzing the test basis
27
Test Basis
The body of knowledge used as the basis for test analysis and design.
28
Test Case
A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.
29
Test Completion
The activity that makes testware available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.
30
Test Condition
A testable aspect of a component or system identified as a basis for testing.
31
Test Control
The activity that develops and applies corrective actions to get a test project on track when it deviates from what was planned. See also: test management
32
Test Data
Data needed for test execution. Synonyms: test dataset
33
Test Design
The activity that derives and specifies test cases from test conditions
34
Test Execution
The activity that runs a test on a component or system producing actual results.
35
Test Implementation
The activity that prepares the testware needed for test execution based on test analysis and design.
36
Test Monitoring
The activity that checks the status of testing activities, identifies any variances from planned or expected, and reports status to stakeholders.
37
Test Object
The work product to be tested. See also: test item
38
Test Objective
The purpose for testing. Synonyms: test goal
39
Test Planning
The activity of establishing or updating a test plan
40
Test Procedure
A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post execution.
41
Test Result
The consequence/outcome of the execution of a test. Synonyms: outcome, test outcome, result
42
Testing
The process within the software development lifecycle that evaluates the quality of a component or system and related work products. See also: quality control
43
Testware
Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing. Reference: After ISO 29119-1
44
Validation
Confirmation by examination that a work product matches a stakeholder's needs
45
Verification
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled
46