Glossary Flashcards Preview

ISTQB Foundation Level 2011 > Glossary > Flashcards

Flashcards in Glossary Deck (165)
Loading flashcards...
1

defect, bug, fault

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.

2

error, mistake

A human action that produces an incorrect result.

3

failure

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

4

quality

The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.

5

risk

A factor that could result in future negative consequences.

6

debugging

The process of finding, analyzing and removing the causes of failures in software.

7

requirement

A provision that contains criteria to be fulfilled.

8

review

A type of static testing during which a work product or process is evaluated by one or more individuals to detect issues and to provide improvements.

9

test case

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

10

testing

The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.

11

test objective

A reason or purpose for designing and executing a test.

12

exhaustive testing, complete testing

A test approach in which the test suite comprises all combinations of input values and preconditions.

13

confirmation testing, re-testing

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

14

exit criteria, completion criteria, test completion criteria, definition of done

The set of conditions for officially completing a defined task.

15

incident, deviation, software test incident, test incident

An event occurring that requires investigation.

16

regression

A degradation in the quality of a component or system due to a change.

17

regression testing

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.

18

test basis

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

19

test condition, test requirement, test situation

An aspect of the test basis that is relevant in order to achieve specific test objectives.

20

coverage, test coverage

The degree to which specified coverage items have been determined or have been exercised by a test suite expressed as a percentage.

21

test data

Data created or selected to satisfy the execution preconditions and inputs to execute one or more test cases.

22

test execution

The process of running a test on the component or system under test, producing actual result(s).

23

test log, test record, test run log

A chronological record of relevant details about the execution of tests.

24

test plan

Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities.

25

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.

26

test policy, organizational test policy

A high-level document describing the principles, approach and major objectives of the organization regarding testing.

27

test suite, test case suite, test set

A set of test cases or test procedures to be executed in a specific test cycle.

28

test summary report, test report

A test report that provides an evaluation of the corresponding test items against exit criteria

29

testware

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

30

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.