test design technique

Question 1

test design technique
test specification technique
test technique
test case design technique

Answer 1

Procedure used to derive and/or select test cases.

Question 2

traceability

Answer 2

The ability to identify related items in documentation and software, such as requirements with associated tests.

Question 3

test script

Answer 3

Commonly used to refer to a test procedure specification, especially an automated one.

Question 4

experience-based technique

experience-based test design technique

Answer 4

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

Question 5

partition testing
equivalence partitioning
equivalence class

Answer 5

A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification.

Question 6

boundary value analysis

boundary value testing

Answer 6

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

Question 7

cause-effect decision

table decision table

Answer 7

A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects), which can be used to design test cases.

Question 8

finite state testing

state transition testing

Answer 8

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

Question 9

state diagram

Answer 9

A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another.

Question 10

state table

Answer 10

A grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions.

Question 11

use case testing

Answer 11

A black box test design technique in which test cases are designed to execute scenarios of use cases.

Question 12

instrumentation

Answer 12

The insertion of additional code into the program in order to collect information about program behavior during execution, e.g. for measuring code coverage.

Question 13

statement coverage

Answer 13

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

Question 14

error guessing

Answer 14

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 15

exploratory testing

Answer 15

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 16

test case specification

Answer 16

A document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) for a test item.

Question 17

black box test design technique
black box technique
specification-based technique
specification-based test design technique

Answer 17

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 18

decision table testing

Answer 18

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 19

decision coverage

Answer 19

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

Question 20

attack

fault attack

Answer 20

Directed and focused attempt to evaluate the quality, especially reliability, of a test object by attempting to force specific failures to occur.

Question 21

attack-based testing

Answer 21

An experience-based testing technique that uses software attacks to induce failures, particularly security related failures.

Question 22

syntax testing

Answer 22

A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.

Question 23

LCSAJ testing

Answer 23

A white box test design technique in which test cases are designed to execute LCSAJs.

Question 24

LCSAJ

Answer 24

A Linear Code Sequence And Jump, consists of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements, the end of the linear sequence, and the target line to which control flow is transferred at the end of the linear sequence.

Question 25

pairwise testing

Answer 25

A black box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters.

Question 26

process cycle test

Answer 26

A black box test design technique in which test cases are designed to execute business procedures and processes.

Question 27

random testing

Answer 27

A black box test design technique where test cases are selected, possibly using a pseudo-random generation algorithm, to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performance.

Question 28

user story testing

Answer 28

A black box test design technique in which test cases are designed based on user stories to verify their correct implementation.

Question 29

cause-effect graphing

Answer 29

A black box test design technique in which test cases are designed from cause-effect graphs.

Question 30

classification tree method

Answer 30

A black box test design technique in which test cases, described by means of a classification tree, are designed to execute combinations of representatives of input and/or output domains.

Question 31

domain analysis

Answer 31

A black box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together. It builds on and generalizes equivalence partitioning and boundary values analysis. See also boundary value analysis, equivalence partitioning.

Question 32

elementary comparison testing

Answer 32

A black box test design technique in which test cases are designed to execute combinations of inputs using the concept of modified condition decision coverage.

Question 33

modified condition decision testing

Answer 33

A white box test design technique in which test cases are designed to execute single condition outcomes that independently affect a decision outcome.

Question 34

multiple condition testing

Answer 34

A white box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).

Question 35

path testing

Answer 35

A white box test design technique in which test cases are designed to execute paths.

Question 36

statement testing

Answer 36

A white box test design technique in which test cases are designed to execute statements.

Question 37

branch testing

Answer 37

A white box test design technique in which test cases are designed to execute branches.

Question 38

condition testing

Answer 38

A white box test design technique in which test cases are designed to execute condition outcomes.

Question 39

data flow testing

Answer 39

A white box test design technique in which test cases are designed to execute definition-use pairs of variables.

Question 40

decision condition testing

Answer 40

A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes.

Question 41

decision testing

Answer 41

A white box test design technique in which test cases are designed to execute decision outcomes.