ISTQB Chapter 4 - Test Analysis and Design - Keywords

Question 1

Acceptance Criteria

Answer 1

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

Question 2

Acceptance Test-Driven Development

Answer 2

A collaborative approach to development in which the team and customers are using the customers own domain language to understand their requirements, which forms the basis for testing a component or system.

Question 3

Black-Box Test Design Technique

Answer 3

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.

Question 4

Boundary Value Analysis

Answer 4

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

Question 5

Branch Coverage

Answer 5

The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.

Question 6

Checklist-Based Testing

Answer 6

An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.

Question 7

Collaboration-Based Test Approach

Question 8

Coverage

Answer 8

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

Question 9

Coverage Item

Answer 9

An entity or property used as a basis for test coverage, e.g., equivalence partitions or code statements.

Question 10

Decision Table Testing

Answer 10

A black-box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table.

Question 11

Equivalence Partitioning

Answer 11

A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are designed to cover each partition at least once.

Question 12

Error Guessing

Answer 12

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.

Question 13

Experience-Based Test Technique

Answer 13

A procedure to derive and/or select test cases based on the tester’s experience, knowledge and intuition.

Question 14

Exploratory Testing

Answer 14

An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.

Question 15

State Transition Testing

Answer 15

A black-box test design technique in which test cases are designed to execute valid and invalid state transitions.

Question 16

Statement Coverage

Answer 16

The percentage of executable statements that have been exercised by a test suite.

Question 17

Test Technique

Answer 17

A procedure used to derive and/or select test cases.

Question 18

White-Box (Technique / Test Design Technique / Test Technique)

Answer 18

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

Question 19

Test Case

Answer 19

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.