Version History

Revision
Draft
Review 01
Instructions
1 Generate the test cases/scenarios based on the Requirements/Specifications documents and list them sequentially in Test Cases worksheet. Make sure that the requirement Ids are mapped to associated test case/script as per the reporting requirment
2 How to add more test case templates on 'Test Cases' sheet?
Add multiple test scripts by selecting cell range A1 to B9 and dragging it down . Also make sure that the formulae are modified as per the reference in 'Column B' of 'Test Cases' work sheet. (Use Test Case 1 for more info and references)
3 How to add more test script templates on 'Test Execution' sheet?
Add multiple test scripts by selecting cell range B2 to I15 and dragging it down . Also make sure that the formulae are modified as per the reference in 'Test Cases' work sheet. (Use Test Case 1 for more info and references)
4 Presently the template example assumes a one to one relationship between Requirements > Test cases > Test Scripts. However. If given requirement has multiple test cases/conditions/scenarios then subsequent test cases and script references are normalised. For example.
If Requirement# ABC 101 has three test scenarios which at that point are in following order 01, 02 and 03. Also let's assume that the test cases 01, 02 and 03 further 2 test scripts each respectively then the relation ship and sequence should look like:
Requirement#
ABC 101
ABC 101
ABC 101
ABC 101
ABC 101
ABC 101
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, quality characteristic or structural element) derived from associated requirement
Pre-Requisites: One or more pre-cond itions which must be fulfilled before executing the given test case
Test Cycle: Test Phase or phase identifier/number for which given test cases and it's execution log is relevant
Action: User input action to be performed on a system or system component to execute the specific step of the test script
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 and priority
Comments: User comments on the test step under execution
Issue Date Comments Author
############## Suitable for use by all projects Dhan Patil
############## Reviwed by Rob Murry Dhan Patil
Generate the test cases/scenarios based on the Requirements/Specifications documents and list them sequentially in Test Cases worksheet. Make sure that the requirement Ids are mapped to associated test case/script as per the reporting requirment
How to add more test case templates on 'Test Cases' sheet?
Add multiple test scripts by selecting cell range A1 to B9 and dragging it down . Also make sure that the formulae are modified as per the reference in 'Column B' of 'Test Cases' work sheet. (Use Test Case 1 for more info and references)
How to add more test script templates on 'Test Execution' sheet?
Add multiple test scripts by selecting cell range B2 to I15 and dragging it down . Also make sure that the formulae are modified as per the reference in 'Test Cases' work sheet. (Use Test Case 1 for more info and references)
Presently the template example assumes a one to one relationship between Requirements > Test cases > Test Scripts. However. If given requirement has multiple test cases/conditions/scenarios then subsequent test cases and script references are normalised. For example.
If Requirement# ABC 101 has three test scenarios which at that point are in following order 01, 02 and 03. Also let's assume that the test cases 01, 02 and 03 further 2 test scripts each respectively then the relation ship and sequence should look like:
Test Case# Test Script#
1 1
1 2
2 3
2 4
3 5
3 6
This ensures user the number of test scripts to be run for given phase/cycle at any point in time
Test Case Objective: Specific element/instance of the test condition (e.g. a function, transaction, quality characteristic or structural element) derived from associated requirement
Pre-Requisites: One or more pre-cond itions which must be fulfilled before executing the given test case
Test Cycle: Test Phase or phase identifier/number for which given test cases and it's execution log is relevant
Action: User input action to be performed on a system or system component to execute the specific step of the test script
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 and priority
Comments: User comments on the test step under execution
Generate the test cases/scenarios based on the Requirements/Specifications documents and list them sequentially in Test Cases worksheet. Make sure that the requirement Ids are mapped to associated test case/script as per the reporting requirment
Add multiple test scripts by selecting cell range A1 to B9 and dragging it down . Also make sure that the formulae are modified as per the reference in 'Column B' of 'Test Cases' work sheet. (Use Test Case 1 for more info and references)
Add multiple test scripts by selecting cell range B2 to I15 and dragging it down . Also make sure that the formulae are modified as per the reference in 'Test Cases' work sheet. (Use Test Case 1 for more info and references)
Presently the template example assumes a one to one relationship between Requirements > Test cases > Test Scripts. However. If given requirement has multiple test cases/conditions/scenarios then subsequent test cases and script references are normalised. For example.
If Requirement# ABC 101 has three test scenarios which at that point are in following order 01, 02 and 03. Also let's assume that the test cases 01, 02 and 03 further 2 test scripts each respectively then the relation ship and sequence should look like:
Test Case Objective: Specific element/instance of the test condition (e.g. a function, transaction, quality characteristic or structural element) derived from associated requirement
Generate the test cases/scenarios based on the Requirements/Specifications documents and list them sequentially in Test Cases worksheet. Make sure that the requirement Ids are mapped to associated test case/script as per the reporting requirment
Presently the template example assumes a one to one relationship between Requirements > Test cases > Test Scripts. However. If given requirement has multiple test cases/conditions/scenarios then subsequent test cases and script references are normalised. For example.
If Requirement# ABC 101 has three test scenarios which at that point are in following order 01, 02 and 03. Also let's assume that the test cases 01, 02 and 03 further 2 test scripts each respectively then the relation ship and sequence should look like:
Test Case# 1
Requirement# ABC 101
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 1
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_06
Test Author Tester_08
Type System Integration
Test Case# 2
Requirement# ABC 102
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 2
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_06
Test Author Tester_08
Type System Integration
Test Case# 3
Requirement# ABC 102
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 3
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_06
Test Author Tester_09
Type System Integration
Test Case# 4
Requirement# ABC 103
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 4
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_05
Test Author Tester_08
Type System Integration
Test Case# 5
Requirement# ABC 103
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 5
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_04
Test Author Tester_07
Type System Integration
Test Case# 6
Requirement# ABC 104
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 6
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_07
Test Author Tester_07
Type System Integration
Test Case# 7
Requirement# ABC 104
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 7
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_06
Test Author Tester_05
Type System Integration
Test Case# 8
Requirement# ABC 105
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 8
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_09
Test Author Tester_04
Type System Integration
Test Case# 9
Requirement# ABC 105
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 9
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_05
Test Author Tester_03
Type System Integration
Test Case# 10
Requirement# ABC 106
Test Case Objective Make sure that this appears as a wrapped text and
represents test conditions derived from the associated
requirement
Test Script# 10
Test Script Name Derived from cell 'Test Case Objective' and could have
one to many relations ship
Priority Low
Functional Area Module_06
Test Author Tester_01
Type System Integration
Test Case# 1
Pre-Requisites
Requirement# Execution Date Executed By
ABC 101
Test Script#
Step# Action Expected Result
1
2
3
4
5
Objective Make sure that this appears as a wrapped text and represents test conditions derived from the associated requirement
1
Status Draft
Release Priority Functional Area Author Test Cycle
Low Module_06 Tester_08
Test Data Actual Result Result Defect(s) Comments
e.g. 'Pass'/'Failed'
Pass/Failed
Pass/Failed
Pass/Failed
Pass/Failed
Make sure that this appears as a wrapped text and represents test conditions derived from the associated requirement
1
Priority FunctionalArea TestAuthor Status Type
High Module_01 Tester_01 Draft Release Test
Low Module_02 Tester_02 Approved Functional
Medium Module_03 Tester_03 Operational
Module_04 Tester_04 Unit
Module_05 Tester_05 Integration
Module_06 Tester_06 System Integration
Module_07 Tester_07 Acceptance
Module_08 Tester_08 Any Other
Module_09 Tester_09
Module_10 Tester_10