Our Resources

1

coverage

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

3

defect

An imperfection or deficiency in a work product where it does not meet its requirements or specifications or impairs its intended use. || See also "error", "failure"

4

error

A human action that produces an incorrect result. || Synonyms: "mistake" || See also "defect"

5

failure

An event in which a component or system does not meet its requirements within specified limits. || See also "defect"

6

quality

The degree to which a work product satisfies stated and implied requirements.

7

quality assurance

Activities focused on providing confidence that quality requirements will be fulfilled. || Abbreviation - QA || See also "quality management"

8

root cause

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

9

test analysis

The activity that identifies test conditions by analyzing the test basis.

10

test basis

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

11

test case

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions. || See also "test step"

12

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.

13

test condition

A testable aspect of a component or system identified as a basis for testing. || Synonyms: "test situation", "test requirement"

14

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"

15

test data

Data needed for test execution. || Synonyms: "test dataset"

16

test design

The activity that derives and specifies test cases from test conditions.

17

test execution

The activity that runs a test on a component or system producing actual results.

18

test implementation

The activity that prepares the testware needed for test execution based on test analysis and design.

19

test monitoring

The activity that checks the status of testing activities, identifies any variances from planned or expected, and reports status to stakeholders. || See also "test management"

20

test object

The work product to be tested. || See also "test item"

21

test objective

The purpose for testing. || Synonyms: "test goal"

22

test planning

The activity of establishing or updating a test plan.

23

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.

24

test result

The consequence/outcome of the execution of a test. || Synonyms: "outcome", "test outcome", "result"

25

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"

26

testware

Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing.

27

validation

Confirmation by examination that a work product matches a stakeholder's needs.

28

verification

The process of confirming that a work product fulfills its specification.

29

acceptance testing

A test level that focuses on determining whether to accept the system. || See also "user acceptance testing"

30

black-box testing

Testing based on an analysis of the specification of the component or system. || Synonyms: "specification-based testing"

31

component integration testing

The integration testing of components. || Synonyms: "module integration testing", "unit integration testing"

32

component testing

A test level that focuses on individual hardware or software components. || Synonyms: "module testing", "unit testing"

33

confirmation testing

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

34

functional testing

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

35

integration testing

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

36

maintenance testing

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

37

non-functional testing

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

38

regression testing

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

39

shift-left

A test approach to perform testing and quality assurance activities as early as possible in the software development lifecycle. || See also "shift-right"

40

system integration testing

The integration testing of systems.

41

system testing

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

42

test level

A specific instantiation of a test process. || Synonyms: "test stage"

43

test step

A single interaction between an actor and a test object consisting of an input, an action, and an expected result. || See also "test case"

44

test type

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

45

white-box testing

Testing based on an analysis of the internal structure of the component or system. || Synonyms: "clear-box testing", "code-based testing", "glass-box testing", "logic-coverage testing", "logic-driven testing", "structural testing", "structure-based testing"

46

anomaly

A condition that deviates from expectation.

47

dynamic testing

Testing that involves the execution of the test item. || See also "static testing"

48

formal review

A review that follows a defined process with a formally documented output.

49

informal review

A type of review that does not follow a defined process and has no formally documented output.

50

inspection

A type of formal review that uses defined team roles and measurement to identify defects in a work product, and improve the review process and the software development process. || See also "peer review"

51

review

A type of static testing in which the quality of a work product or process is evaluated by individuals. || See also "static testing"

52

static analysis

The process of evaluating a component or system without executing it, based on its form, structure, content, or documentation. || See also "static testing"

53

static testing

Testing that does not involve the execution of a test item. || See also "dynamic testing", "static analysis", "review"

54

technical review

A formal review by technical experts that examine the quality of a work product and identify discrepancies from specifications and standards. || See also "peer review"

55

walkthrough

A type of review in which an author leads members of the review through a work product and the members ask questions and make comments about possible issues. || Synonyms: "structured walkthrough" || See also "peer review"

56

acceptance criteria

The criteria that a work product must satisfy to be accepted by the stakeholders.

57

acceptance test-driven development

A collaboration-based test-first approach that defines acceptance tests in the stakeholders' domain language. || Abbreviation - ATDD || See also "specification by example"

58

black-box test technique

A test technique based on an analysis of the specification of a component or system. || Synonyms: "black-box test design technique", "specification-based test technique"

59

boundary value analysis

A black-box test technique in which test cases are designed based on boundary values. || See also "boundary value"

60

branch coverage

The coverage of branches in a control flow graph.

61

checklist-based testing

An experience-based test technique in which test cases are designed to exercise the items of a checklist.

62

collaboration-based test approach

An approach to testing that focuses on defect avoidance by collaborating among stakeholders.

63

test item

A part of a test object used in the test process. || See also "test object"

64

coverage item

An attribute or combination of attributes derived from one or more test conditions by using a test technique.

65

decision table testing

A black-box test technique in which test cases are designed to exercise the combinations of conditions and the resulting actions shown in a decision table.

66

equivalence partitioning

A black-box test technique in which test conditions are equivalence partitions exercised by one representative member of each partition. || Synonyms: "partition testing"

67

error guessing

A test technique in which tests are derived on the basis of the tester's knowledge of past failures, or general knowledge of failure modes.

68

experience-based test technique

A test technique based on the tester's experience, knowledge and intuition. || Synonyms: "experience-based test design technique", "experience-based technique"

69

exploratory testing

An approach to testing in which the testers dynamically design and execute tests based on their knowledge, exploration of the test item and the results of previous tests. || See also "test charter"

70

state transition testing

A black-box test technique in which test cases are designed to exercise elements of a state transition model. || Synonyms: "finite state testing"

71

statement coverage

The coverage of executable statements.

72

test technique

A procedure used to define test conditions, design test cases, and specify test data. || Synonyms: "test design technique"

73

white-box test technique

A test technique only based on the internal structure of a component or system. || Synonyms: "white-box test design technique", "structure-based test technique"

74

defect management

The process of recognizing, recording, classifying, investigating, fixing and disposing of defects.

75

defect report

Documentation of the occurrence, nature, and status of a defect. || Synonyms: "bug report"

76

entry criteria

The set of conditions for officially starting a defined task. || See also "exit criteria"

77

exit criteria

The set of conditions for officially completing a defined task. || Synonyms: "test completion criteria", "completion criteria" || See also "entry criteria"

78

product risk

A risk that impacts the quality of a product. || See also "risk"

79

project risk

A risk that impacts project success. || See also "risk"

80

risk

A factor that could result in future negative consequences. || See also "product risk", "project risk"

81

risk analysis

The overall process of risk identification and risk assessment.

82

risk assessment

The process to examine identified risks and determine the risk level.

83

risk control

The overall process of risk mitigation and risk monitoring.

84

risk identification

The process of finding, recognizing and describing risks.

85

risk level

The measure of a risk defined by risk impact and risk likelihood. || Synonyms: "risk exposure"

86

risk management

The process for handling risks.

87

risk mitigation

The process through which decisions are reached and protective measures are implemented for reducing or maintaining risks to specified levels.

88

risk monitoring

The activity that checks and reports the status of known risks to stakeholders.

89

risk-based testing

A test approach in which the management, selection, prioritization, and use of test activities and resources are based on corresponding risk types and risk levels.

90

test approach

The manner of implementing testing tasks.

91

test completion report

A type of test report produced at completion milestones that provides an evaluation of the corresponding test items against exit criteria. || Synonyms: "test summary report"

92

quality control

Activities designed to evaluate the quality of a component or system. || Abbreviation - QC || See also "testing"

93

user acceptance testing

A type of acceptance testing performed to determine if intended users accept the system. Abbreviation - UAT || See also "acceptance testing"

94

test plan

Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities. || See also "master test plan", "level test plan", "test scope"

95

test management

The process of planning, scheduling, estimating, monitoring, reporting, controlling, and completing test activities. || See also "test control", "test monitoring"

96

test progress report

A type of periodic test report that includes the progress of test activities against a baseline, risks, and alternatives requiring a decision. || Synonyms: "test status report"

97

test pyramid

A graphical model representing the relationship of the amount of testing per level, with more at the bottom than at the top.

98

testing quadrants

A classification model of test types/test levels in four quadrants, relating them to two dimensions of test objectives: supporting the product team versus critiquing the product, and technology-facing versus business-facing.

99

quality management

The process of establishing and directing a quality policy, quality objectives, quality planning, quality control, quality assurance, and quality improvement for an organization. || See also "quality assurance"

100

test automation

The conversion of test activities to automatic operation.

101

shift-right

A test approach to test a system continuously in production. || See also "shift-left", "testing in production"

102

peer review

A type of review performed by others with the same abilities to create the work product. || See also "technical review", "inspection", "walkthrough"

103

specification by example

A development technique in which the specification is defined by examples. || Abbreviation - SBE || See also "acceptance test-driven development"

104

boundary value

A minimum or maximum value of an ordered equivalence partition. || See also "boundary value analysis"

105

test charter

Documentation of the goal or objective for a test session. || Synonyms "charter" || See also "exploratory testing"

106

master test plan

A test plan that is used to coordinate multiple test levels or test types. || See also "test plan"

107

level test plan

A test plan that typically addresses one test level. || See also "test plan"

108

test scope

A description of the test object and its features to be tested. || See also "test plan"

109

testing in production

A test type performed in the production environment with live data. || See also "post-release testing", "shift-right"

110

post-release testing

A test level performed after the release of a system to validate that it can be deployed in operational environments. || See also "testing in production"