Version History
Revision
Draft
Review 01
Issue Date
Comments
### Suitable for use by all projects
### Reviwed by Rob Murry
Author
Dhan Patil
Dhan Patil
Instructions
Generate the test cases/scenarios based on the Requirements/Specifications documents and list them seque
Presently the template example assumes a one to one relationship between Requirements > Test cases > Te
If Requirement# ABC 101 has three test scenarios which at that point are in following order 01, 02 and 03. A
Requirement#
Test Case#
Test Script#
ABC 101
1
1
ABC 101
1
2
ABC 101
2
3
ABC 101
2
4
ABC 101
3
5
ABC 101
3
6
This ensures user the number of test scripts to be run for given phase/cycle at any point in time
Terminology
Test Case Objective: Specific element/instance of the test condition (e.g. a function, transaction,
Pre-Requisites: One or more pre-cond itions which must be fulfilled before executing the given te
Test Cycle: Test Phase or phase identifier/number for which given test cases and it's execution log
Action: User input action to be performed on a system or system component to execute the speci
Expected Result: Anticipated outcome to the user input action
Actual Result: Observed outcome to the user input action
Test Data: : Specific values required along with the user action to achieve expected result
Result: Test script or Test script step outcome (Pass, Failed, Not Completed)
Defect(s): Deviation of actual result from the expected result often expressed in terms of severity
nts and list them sequentially in Test Cases worksheet. Make sure that the requirement Ids are mapped to associated te
make sure that the formulae are modified as per the reference in 'Column B' of 'Test Cases' work sheet. (Use Test Case
make sure that the formulae are modified as per the reference in 'Test Cases' work sheet. (Use Test Case 1 for more info
ents > Test cases > Test Scripts. However. If given requirement has multiple test cases/conditions/scenarios then subse
order 01, 02 and 03. Also let's assume that the test cases 01, 02 and 03 further 2 test scripts each respectively then th
int in time
unction, transaction, quality characteristic or structural element) derived from associated requirement
xecuting the given test case
and it's execution log is relevant
to execute the specific step of the test script
pected result
ses' work sheet. (Use Test Case 1 for more info and references)
conditions/scenarios then subsequent test cases and script references are normalised. For example.
scripts each respectively then the relation ship and sequence should look like:
associated requirement
For example.
Test Case#
Requirement#
ABC 101
Test Script#
Test Script Name
Priority
Low
Module_06
Tester_08
System Integration
Functional Area
Test Author
Type
Test Case#
Requirement#
ABC 102
Test Script#
Test Script Name
Priority
Low
Module_06
Tester_08
System Integration
Functional Area
Test Author
Type
Test Case#
Requirement#
ABC 102
Test Script#
Test Script Name
Priority
Low
Module_06
Tester_09
System Integration
Functional Area
Test Author
Type
Test Case#
Requirement#
ABC 103
Test Script#
Test Script Name
Priority
Low
Module_05
Tester_08
Functional Area
Test Author
Type
System Integration
Test Case#
Requirement#
ABC 103
Test Script#
Test Script Name
Priority
Low
Module_04
Tester_07
System Integration
Functional Area
Test Author
Type
Test Case#
Requirement#
ABC 104
Test Script#
Test Script Name
Priority
Low
Module_07
Tester_07
System Integration
Functional Area
Test Author
Type
Test Case#
Requirement#
ABC 104
Test Script#
Test Script Name
Priority
Low
Module_06
Tester_05
System Integration
Functional Area
Test Author
Type
Test Case#
Requirement#
ABC 105
Test Script#
Test Script Name
Priority
Low
Module_09
Functional Area
Test Author
Type
Tester_04
System Integration
Test Case#
Requirement#
ABC 105
Test Script#
Test Script Name
Priority
Low
Module_05
Tester_03
System Integration
Functional Area
Test Author
Type
Test Case#
10
Requirement#
ABC 106
Test Script#
Test Script Name
Priority
Low
Module_06
Tester_01
System Integration
Functional Area
Test Author
Type
Test Case#
Objective
Pre-Requisites
Requirement#
Make sure that this appears as a wrapped text and represents test conditions d
Execution Date
ABC 101
Test Script#
Step#
1
2
3
4
5
Action
rs as a wrapped text and represents test conditions derived from the associated requirement
Executed By
Release
1
Expected Result
Test Data
Status
Draft
ciated requirement
Priority
Functional Area
Low
Module_06
Actual Result
Result
e.g. 'Pass'/'Failed'
Pass/Failed
Pass/Failed
Pass/Failed
Pass/Failed
Author
Test Cycle
Tester_08
Defect(s)
Comments
Priority
High
Low
Medium
FunctionalArea
Module_01
Module_02
Module_03
Module_04
Module_05
Module_06
Module_07
Module_08
Module_09
Module_10
TestAuthor
Tester_01
Tester_02
Tester_03
Tester_04
Tester_05
Tester_06
Tester_07
Tester_08
Tester_09
Tester_10
Status
Draft
Approved
Type
Release Test
Functional
Operational
Unit
Integration
System Integration
Acceptance
Any Other