Istqb Chapter 4

Front 1

All of the input values, execution preconditions, expected results, and expected postconditions defined to cover certain test objectives or conditions.

Back 1

Test cases

Front 2

What does the following chart represent?

Test design -> Test case -> Test procedure

Back 2

IEEE 829-1998 Standard for Software Test Documentation

Front 3

What is the test development process?

Back 3

1. Test analysis

2. Test conditions are identified.

3. Test cases and data are created.

Front 4

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

Back 4

Test design technique

Front 5

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

Back 5

Test design specification

Front 6

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

Back 6

Test case specification

Front 7

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

AKA- Test script, manual test script

Back 7

Test procedure specification

Front 8

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

Back 8

Test script

Front 9

Artifacts produced during the test process required to plan, design, and execute expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.

Back 9

Testware

Front 10

All of the following are methods for what type of testing?

- Statement Testing

- Condition Testing

- Decision Testing

- Multiple Condition Testing

Back 10

Structure based testing

Front 11

White-box testing that is based on the internal workings of a given system. Aimed at finding issues with the structure as opposed to the function of the system.

Back 11

Structure based testing

Front 12

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

Back 12

Statement testing

Front 13

The smallest standalone element of a program.

Back 13

Statement

Front 14

Assessment of the percentage of executable statements that have been executed by a test case suite.

Back 14

Statement coverage

Front 15

In a given system, different input can yield different outputs. ______ checks the combinations of inputs and outputs.

Back 15

Decision testing

Front 16

A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions.

Back 16

Equivalence partitioning

Front 17

- State transition

- Decision tables

- Boundary value analysis

- Equivalence partitioning

- Use cases

Are all parts of what type of testing?

Back 17

Specification based testing

Front 18

"A piece of armor requires you to have at least 110 strength to use, what are the boundary values of this?"

This exercise is an example of ______.

Back 18

Boundary value analysis

Front 19

Testing that looks at the combinations of variables and their outcomes. This is used to test combinations of rules.

Back 19

Decision tables

Front 20

The transition between states of a component or system. A black-box test design technique in which test cases are designed to execute valid and invalid state transitions.

AKA- N-switch testing.

Back 20

State transition

Front 21

The sequence of transactions in a dialogue between a user and the system with a tangible result. A black-box technique in which test cases are designed to execute user scenarios.

Back 21

Use case

Front 22

- Error guessing

- Exploratory testing

These are components of what type of testing?

Back 22

Experience based testing

Front 23

Revolves around trying to predict where issues would occur and creating tests to check them. Utilizes fault attacks.

Back 23

Error guessing

Front 24

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

Back 24

Fault attack

Front 25

Encourages exploring a program as opposed to systematically testing the software. The information gathered through this is used to build new test cases.

Back 25

Exploratory testing

Front 26

Statement of test objectives and possible ideas about how to test. Used in exploratory testing.

Back 26

Test charter