The Test Development Process

6/27/12

Terms

Test case specification

A detail of the specific data that is necessary to run tests based on the conditions identified in the previous stage.

Test design
A detail of the test conditions and the expected outcome. This document also includes details of how a successful test will be recognized.

6/27/12

Terms

Test execution schedule

A series of tasks, or steps, that can be run sequentially at a scheduled time.

Test procedure specification

A detail of how the tester will physically run the test, the physical set-up required, and the procedure steps that need to be followed. 6/27/12

Terms

Test script
is a set of instructions that will be performed on the system under test to test that the system functions as expected.

Traceability

refers to the ability to link product documentation requirements back to stakeholders' rationales and forward to 6/27/12 corresponding design artifacts, code, and

Categories of Test Design Techniques

Click to edit Master subtitle style

6/27/12

Terms Black-box test design technique Experience-based test design technique Test design technique White-box test design 6/27/12 technique

Background

The purpose of a test design technique is to identify test conditions, test cases, and test data.

6/27/12

Characteristics of specification-based test design techniques (Black-box

techniques)

Models, either formal or informal, are used for the specification of the problem to be solved, the software or its components Test cases can be derived systematically from these models

6/27/12

Characteristics of structure-based test design techniques (White-box

techniques)

Information about how the software is constructed is used to derive the test cases (e.g., code and detailed design information)

The extent of coverage of the software can be measured for existing test cases, and further test cases can be derived systematically to increase 6/27/12

Characteristics of experience-based test Experience- based design techniques(

techniques)

The knowledge and experience of people are used to derive the test cases The knowledge of testers, developers, users and other stakeholders about the software, its usage and its environment is one source of information Knowledge about likely defects and

6/27/12

Specificationbased or Black-box Techniques

6/27/12

Terms

Boundary value analysis Decision table testing Equivalence partitioning State transition testing Use case testing

6/27/12

Equivalence Partitioning

is a software testing technique that divides the input data of a software unit into partitions of data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once. This technique tries to define test cases that uncover classes of errors, thereby reducing the total number of test cases that must be developed. 6/27/12

Equivalence Partitioning

Equivalence partitioning can be used to achieve input and output coverage goals. It can be applied to human input, input via interfaces to a system, or interface parameters in integration testing.

6/27/12

Boundary Value Analysis

is a software testing technique in which tests are designed to include representatives of boundary values. Values on the minimum and maximum edges of an equivalence partition are tested. The values could be either input or output ranges of a software component. Since these boundaries are common 6/27/12 locations for errors that result in software

Decision Table Testing

lists all the input conditions that can occur and all the actions that can arise from them. These are structured into a table as rows, with the conditions at the top of the table and the possible actions at the bottom. Business rules, which involve combinations of conditions to produce some combination of 6/27/12

State Transition Testing

A state transition diagram is a representation of the behavior of a system

6/27/12

State Diagram

A state is just what it says it is: the system is static, in a stable 6/27/12

Transition Diagram

A change from one state to another

6/27/12

Use Case Testing

Description of steps or actions between a user and a software system which leads the user towards something useful

6/27/12