Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

computer testing terms > testing terms > Flashcards

testing terms Flashcards

1
Q

acceptance test-driven development

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
2
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
3
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
4
Q

actual result

A

The behavior produced/observed when a component or system is tested.

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

Agile software development

A

A group of software development methodologies based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

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

alpha testing

A

A type of acceptance testing performed in 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
7
Q

anomaly

A

A condition that deviates from expectation.

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

API testing

A

Testing performed by submitting requests to the test object using its application programming interface.

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

audit

A

An independent examination of a work product or process performed by a third party to assess whether it complies with specifications, standards, contractual agreements, or other criteria.

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

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

black-box test technique

A

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

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

black-box testing

A

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

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

branch

A

A transfer of control between two 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
18
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
19
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
20
Q

cause-effect diagram

A

A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or potential defect or failure are organized in categories and subcategories in a horizontal tree-structure, with the (potential) defect or failure as the root node.

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

checklist-based review

A

A review technique guided by a list of questions or required attributes.

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

checklist-based testing

A

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

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

coding standard

A

A standard that describes the characteristics of a design or a design description of data or program components.

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

collaboration-based test approach

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
compatibility
The degree to which a component or system can exchange information with other components or systems, and/or perform its required functions while sharing the same hardware or software environment.
26
complexity
The degree to which the design or code of a component or system is difficult to understand.
27
compliance
Adherence of a work product to standards, conventions or regulations in laws and similar prescriptions.
28
component
A part of a system that can be tested in isolation.
29
component integration testing
The integration testing of components.
30
component testing
A test level that focuses on individual hardware or software components.
31
configuration management
A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify that it complies with specified requirements.
32
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.
33
continuous integration
An automated software development procedure that merges, integrates and tests all changes as soon as they are committed.
34
continuous testing
An approach that involves a process of testing early, testing often, test everywhere, and automate to obtain feedback on the business risks associated with a software release candidate as rapidly as possible.
35
control flow
The sequence in which operations are performed by a business process, component or system.
36
cost of quality
The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure costs.
37
coverage
The degree to which specified coverage items are exercised by a test suite, expressed as a percentage.
38
coverage criteria
The criteria to define the coverage items required to reach a test objective.
39
coverage item
An attribute or combination of attributes derived from one or more test conditions by using a test technique.
40
dashboard
A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual dials, counters, and other devices resembling those on the dashboard of an automobile, so that the effects of events or activities can be easily understood and related to operational goals.
41
debugging
The process of finding, analyzing and removing the causes of failures in a component or system.
42
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.
43
defect
An imperfection or deficiency in a work product where it does not meet its requirements or specifications.
44
defect density
The number of defects per unit size of a work product.
45
Defect Detection Percentage
The number of defects found by a test level, divided by the number found by that test level and any other means afterwards.
46
defect management
The process of recognizing, recording, classifying, investigating, resolving and disposing of defects.
47
defect report
Documentation of the occurrence, nature, and status of a defect.
48
driver
A component or tool that temporarily replaces another component and controls or calls a test item in isolation.
49
dynamic testing
Testing that involves the execution of the test item.
50
effectiveness
The extent to which correct and complete goals are achieved.
51
efficiency
The degree to which resources are expended in relation to results achieved.
52
entry criteria
The set of conditions for officially starting a defined task.
53
equivalence partition
A subset of the value domain of a variable within a component or system in which all values are expected to be treated the same based on the specification.
54
equivalence partitioning
A black-box test technique in which test conditions are equivalence partitions exercised by one representative member of each partition.
55
error
A human action that produces an incorrect result.
56
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.
57
exhaustive testing
A test approach in which the test suite comprises all combinations of input values and preconditions.
58
exit criteria
The set of conditions for officially completing a defined task.
59
expected result
The observable predicted behavior of a test item under specified conditions based on its test basis.
60
experience-based test technique
A test technique based on the tester's experience, knowledge and intuition.
61
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.
62
failed
The status of a test result if the actual result does not match the expected result.
63
failure
An event in which a component or system does not perform a required function within specified limits.
64
feature-driven development
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.
65
finding
A result of an evaluation that identifies some important issue, problem, or opportunity.
66
formal review
A type of review that follows a defined process with a formally documented output.
67
functional appropriateness
The degree to which the functions facilitate the accomplishment of specified tasks and objectives.
68
functional completeness
The degree to which the set of functions covers all the specified tasks and user objectives.
69
functional correctness
The degree to which a component or system provides the correct results with the needed degree of precision.
70
functional testing
Testing performed to evaluate if a component or system satisfies functional requirements.
71
heuristic
A generally recognized rule of thumb that helps to achieve a goal.
72
impact analysis
The identification of all work products affected by a change, including an estimate of the resources needed to accomplish the change.
73
incremental development model
A type of software development lifecycle model in which the component or system is developed through a series of increments.
74
independence of testing
Separation of responsibilities, which encourages the accomplishment of objective testing.
75
informal review
A type of review that does not follow a defined process and has no formally documented output.
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100

computer testing terms (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions