Test design involves authoring of test cases. What is a Test case?
IEEE Standard 610 (1990) defines test case as follows:
“(1) A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
“(2) (IEEE Std 829-1983) Documentation specifying inputs, predicted results, and a set of execution conditions for a test item.” Test Case Design Techniques
Black box Design Techniques:
a. Equivalence Class Partitioning
b. Boundary Value Analysis
c. Decision Table Testing
d. State Transition Testing
e. Use Case Testing
f. Error Guessing Technique
White Box Design Techniques:
a. Control Flow Testing
b. Data Flow Testing
c. Decision Coverage
d. Statement coverage
Key Points to be followed in Designing
A Test case should
a. Start with the word verify or check
b. Contain a maximum of 15 steps
c. Specify what the tester has to perform
d. Give consistent results irrespective of testers
e. Be divided into positive and negative scenarios
f. Has a name and number
g. Should be reusable
h. Should be simple and easy to understand
Test Case Format
As per the IEEE format a test case should contain the following
a. Test case Id
b. Requirement ID
c. Test Case priority
d. Test Case Authoring Status
e. Authoring Date
f. Test Case Title
g. Pre-Condition
h. Test Data
i. Test Steps
j. Expected Result
k. Actual result
l. Execution status
m. Defect Id
n. Defect Severity
o. Execution Date
In general it can be as follows
Ex: A Test Case to open Note pad
| Step no | Steps to perform | Expected Result | Actual Result |
| 1 | Click on ‘Start’ Menu on the Left hand bottom of the screen | A window containing ‘all programs’ is displayed | Same as Expected |
| 2 | Click on ‘Run’ | A run window is opened with label ‘open’ | Run window is successfully opened |
| 3 | Enter ‘Notepad’ in the text box and click on ok button | Notepad is opened with File, Edit, Format, View and help menu | Note pad is successfully opened |