Istqb F.l. Glossary Chapters 1 & 2

Front 1

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.

Back 1

Requirement

Front 2

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

Back 2

Debugging

Front 3

A set of input values, execution preconditions, expected results and execution postconditions developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.

Back 3

Test Case

Front 4

An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements.

Back 4

Review

Front 5

A reason or purpose for designing and executing a test.

Back 5

Test Objective

Front 6

A flaw in a component or system that can cause the component or system to fail to perform its required function.

Back 6

Bug - Defect - Fault

Front 7

A human action that produces an incorrect result.

Back 7

Error - Mistake

Front 8

Deviation of the component or system from its expected delivery, service or result.

Back 8

Failure

Front 9

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

Back 9

Quality

Front 10

A factor that could result in future negative consequences; usually expressed as impact and likelihood.

Back 10

Risk

Front 11

The process consisting of all life cycle 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.

Back 11

Testing

Front 12

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

Back 12

Exhaustive Testing

Front 13

The set of generic and specific conditions, agreed upon with the stakeholders, for permitting a process to be officially completed.

Back 13

Exit Criteria

Front 14

Any event occurring that requires investigation.

Back 14

Incident

Front 15

Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software as a result of the changes made. It is performed when the software or its environment is changed.

Back 15

Regression Testing

Front 16

All documents from which the requirements of a component or system can be inferred.

Back 16

Test Basis

Front 17

An item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, feature, quality attribute, or structural element.

Back 17

Test Condition

Front 18

The degree, expressed as a percentage, to which a specified c_______ item has been exercised by a test suite.

Back 18

Coverage - Test Coverage

Front 19

Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.

Back 19

Test Data

Front 20

The process of running a test on the component or system under test, producing actual results.

Back 20

Test Execution

Front 21

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

Back 21

Test Log

Front 22

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

Back 22

Test Policy

Front 23

A high-level description of the test levels to be performed and the testing within those levels for an organization or program (one or more projects).

Back 23

Test Strategy

Front 24

A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned.

Back 24

Test Control

Front 25

A test management task that deals with the activities related to periodically checking the status of a test project. Reports are prepared that compare the actuals to that which was planned.

Back 25

Test Monitoring

Front 26

A set of input values, execution preconditions, expected results and execution postconditions developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.

Back 26

Test Case

Front 27

A document specifying the test conditions (coverage items) for a test item, the detailed test approach and the associated high-level test cases.

Back 27

Test Design Specification

Front 28

A document specifying a sequence of actions for the execution of a test.

Back 28

Test Procedure Specification

Front 29

A set of several test cases for a component or system under test, where the postcondition of one test is often used as the precondition for the next one.

Back 29

Test Suite

Front 30

Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.

Back 30

Retesting - Confirmation Testing

Front 31

A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria.

Back 31

Test Summary Report

Front 32

Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used

Back 32

Testware

Front 33

Separation of responsibilities, which encourages the accomplishment of objective testing.

Back 33

Independence

Front 34

A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them.

Back 34

Error Guessing

Front 35

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the __________ criteria and to enable the user, customers or other authorized entity to determine whether or not to ______ the system.

Back 35

Acceptance testing

Front 36

Simulated or actual operational testing by potential users/customers or an independent test team at the developers site, but outside the development organization. _____ _______ is often employed for off-the-shelf software as a form of internal acceptance testing.

Back 36

Alpha testing

Front 37

Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes.

Back 37

Beta testing

Front 38

The testing of individual software c__________.

Back 38

Component testing

Front 39

A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.

Back 39

Driver

Front 40

A ___________ that specifies a function that a component or system must perform.

Back 40

Functional requirement

Front 41

A development life cycle where a project is broken into a series of __________.

Back 41

Incremental development model

Front 42

The process of combining components or systems into larger assemblies.

Back 42

Integration

Front 43

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

Back 43

Integration testing

Front 44

A ___________ that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.

Back 44

Non-functional requirement

Front 45

A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.

Back 45

Off-the-shelf software

Front 46

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.

Back 46

Requirement

Front 47

The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.

Back 47

Robustness

Front 48

Testing to determine the ro________ of the software product.

Back 48

Robustness testing

Front 49

A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component.

Back 49

Stub

Front 50

The process of testing an integrated ______ to verify that it meets specified requirements.

Back 50

System testing

Front 51

A way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.

Back 51

Test driven development

Front 52

An ___________ containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.

Back 52

Test environment

Front 53

A group of test activities that are organized and managed together.

Back 53

Test level

Front 54

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

Back 54

Validation

Front 55

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.

Back 55

Verification

Front 56

A framework to describe the software development life cycle activities from requirements specification to maintenance.

Back 56

V-model

Front 57

A group of test activities aimed at testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test etc.

Back 57

Test type

Front 58

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

Back 58

Functional testing

Front 59

Testing, either functional or non-functional, without reference to the internal structure of the component or system.

Back 59

Black-box testing

Front 60

Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its internal structure.

Back 60

Black-box test design technique

Front 61

The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions.

Back 61

Functionality

Front 62

The process of testing to determine the f____________ of a software product.

Back 62

Functionality testing

Front 63

The capability of the software product to interact with one or more specified components or systems.

Back 63

Interoperability

Front 64

The process of testing to determine the i_______________ of a software product.

Back 64

Interoperability testing

Front 65

Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.

Back 65

Security

Front 66

Testing to determine the s_______ of the software product.

Back 66

Security testing

Front 67

A type of performance testing conducted to evaluate the behavior of a component or system with increasing ____, e.g. numbers of parallel users and/or numbers of transactions, to determine what ____ can be handled by the component or system.

Back 67

Load testing

Front 68

The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.

Back 68

Performance

Front 69

The process of testing to determine the pe_________ of a software product. See also efficiency testing.

Back 69

Performance testing

Front 70

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements.

Back 70

Stress testing

Front 71

The process of testing to determine the re_________ of a software product.

Back 71

Reliability testing

Front 72

The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions.

Back 72

Usability

Front 73

Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and attractive to the users under specified conditions.

Back 73

Usability testing

Front 74

The capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions.

Back 74

Efficiency

Front 75

The process of testing to determine the e_________ of a software product.

Back 75

Efficiency testing

Front 76

The ease with which the software product can be transferred from one hardware or software environment to another.

Back 76

Portability

Front 77

The process of testing to determine the po_________ of a software product.

Back 77

Portability testing

Front 78

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

Back 78

White-box testing (structural testing)

Front 79

An analysis method that determines which parts of the software have been executed, _______ by the test suite and which parts have not been executed.

Back 79

Code coverage

Front 80

Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.

Back 80

White-box test design technique

Front 81

Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.

Back 81

Maintenance

Front 82

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

Back 82

Maintenance testing

Front 83

The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment.

Back 83

Maintainability

Front 84

The process of testing to determine the m______________ of a software product.

Back 84

Maintainability testing

Front 85

The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.

Back 85

Impact analysis