Professional Documents
Culture Documents
Testoutline Template
Testoutline Template
Author:
Current Owner:
Creation Date:
Last Updated:
Document Version:
Status: Draft/In Process/Approved
1. Document Control
Change History
Name Position Date Document Description of Change Including Section of outline
Version
Document References
Name Type of Reference Document Location
Page 2 of 6
Table of Contents
1.DOCUMENT CONTROL..................................................................................................................................................................................................................................2
CHANGE HISTORY.....................................................................................................................................................................................................................................................2
REVIEW AND APPROVAL HISTORY................................................................................................................................................................................................................................2
DOCUMENT REFERENCES ...........................................................................................................................................................................................................................................2
PROJECTS COVERED IN TEST OUTLINE.........................................................................................................................................................................................................................2
2.TRACEABILITY MATRIX...............................................................................................................................................................................................................................4
Requirements/ Features / Sub Features...........................................................................................................................................................................................................4
3.TEST OUTLINES...............................................................................................................................................................................................................................................5
<TEST CASE ID1>-<TEST CASE NAME1>.................................................................................................................................................................................................................5
<TEST CASE ID2>-<TEST CASE NAME2>.................................................................................................................................................................................................................5
4.EFFORT ESTIMATES.......................................................................................................................................................................................................................................6
Page 3 of 6
2. TRACEABILITY MATRIX
DD_ID
Comments
Test Case Type (N-New, E-Exist) N N N E
Requirements/ Features / Sub Features
Feature1 4 X X
Subfeature1.1 4.2.1 X
Subfeature1.2 4.2.2 X
Subfeature1.3 4.2.3 X
Subfeature1.4 4.2.4 X
Feature2 5 X X
Subfeature2.1 5.1.1 X
Subfeature2.2 5.1.2 X
Subfeature2.3 5.1.3 X
Subfeature2.4 5.1.4 X
Page 4 of 6
3. TEST OUTLINES
Test Objectives:
Specify at a very high level, what the test case is intended to achieve or verify
Process Flow: At a high level, specify what the flow of the test case is.
<user1>: <Flow Name1>
<user2>: <Flow Name2>
…
Test Outline:
S.NO USER ACTION
<user1> <Flow Name1>
The following things should be mentioned here at a high level
• Description of what actions should be performed
1
• What is the type or characteristics of data to be used.
• What should be verified or checked after performing the action.
Test Objectives:
Specify at a very high level, what the test case is intended to achieve or verify
Page 5 of 6
Test Case Dependencies / Assumptions:
Process Flow: At a high level, specify what the flow of the test case is.
<user3>: <Flow Name3>
<user4>: <Flow Name4>
…
Test Outline:
S.NO USER ACTION
<user3> <Flow Name3>
The following things should be mentioned here at a high level
• Description of what actions should be performed
1
• What is the type or characteristics of data to be used.
• What should be verified or checked after performing the action.
4. EFFORT ESTIMATES
Test Case ID Test Case Effort Effort
Priority Required for Required for
(H,M,L) Test Case Manual
writing Execution
(days) (days)
Page 6 of 6