In this session you will learn: Test Case Design and Techniques Test Cases Good Test Cases Test Case Design Technique Black-box: Three major approaches Black-box : Equivalence Partitioning Boundary value analysis

1. Page 1Classification: Restricted
Quality Assurance /
Software Testing Training
TestCase Design and Technique

2. Page 2Classification: Restricted
Agenda
• Test Case Design and Techniques
• Test Cases
• Good Test Cases
• Test Case Design Technique
• Black-box: Three major approaches
• Black-box : Equivalence Partitioning
• Boundary value analysis

3. Page 3Classification: Restricted
Test Case Design and Techniques
TEST CASES
Test case is defined as
A set of test inputs, execution conditions and expected results, developed
for a particular objective.
Documentation specifying inputs, predicted results and a set of execution
conditions for a test item.
Specific inputs that will be tried and the procedures that will be followed
when the software tested.
Sequence of one or more subtests executed as a sequence as the outcome
and/or final state of one subtests is the input and/or initial state of the
next.
Specifies the pretest state of the AUT and its environment, the test inputs
or conditions.
The expected result specifies what the AUT should produce from the test
inputs.

4. Page 4Classification: Restricted
Test Cases
Contents
Test case name
Test case id
Objective
Steps
Expected result
Actual result
Pass/fail
Comments

5. Page 5Classification: Restricted
Good Test Cases
Find Defects
Have high probability of finding a new defect.
Unambiguous tangible result that can be inspected.
Repeatable and predictable
Traceable to requirements or design documents
Push systems to its limits
Execution and tracking can be automated
Do not mislead
Feasible

6. Page 6Classification: Restricted
Test Case Design Technique
Black-box testing (or functional testing):
Equivalence partitioning
Boundary value analysis
Cause-effect graphing
Behavioural testing
Random testing
etc…

7. Page 7Classification: Restricted
Black-box: Three major approaches
Analysis of the input/output domain of the program:
Leads to a logical partitioning of the input/output domain into
‘interesting’ subsets
Analysis of the observable black-box behaviour:
Leads to a flow-graph-like model, which enables application of
techniques from the white-box world (on the black-box model)
Techniques like risk analysis, random input, stress testing

8. Page 8Classification: Restricted
Black-box : Equivalence Partitioning
Equivalence Partitioning also called as equivalence class partitioning. It is
abbreviated as ECP. It is a software testing technique that divides the input
test data of the application under test into each partition at least once of
equivalent data from which test cases can be derived.
An advantage of this approach is it reduces the time required for performing
testing of a software due to less number of test cases.
Example:
The Below example best describes the equivalence class Partitioning:
Assume that the application accepts an integer in the range 100 to 999
Valid Equivalence Class partition: 100 to 999 inclusive. Non-valid
Equivalence Class partitions: less than 100, more than 999, decimal

9. Page 9Classification: Restricted
Boundary value analysis
Boundary value analysis is a type of black box or specification based testing
technique in which tests are performed using the boundary values.
Example:
An exam has a pass boundary at 50 percent, merit at 75 percent and distinction
at 85 percent. The Valid Boundary values for this scenario will be as follows:
49, 50 - for pass
74, 75 - for merit
84, 85 - for distinction
Boundary values are validated against both the valid boundaries and invalid
boundaries.
The Invalid Boundary Cases for the above example can be given as follows:
0 - for lower limit boundary value
101 - for upper limit boundary value

10. Page 10Classification: Restricted