Put your logo here
<Project name / Use Case>
Test Cases
Version <1.0>
.
June 5, 2011
<Project name / Use Case> / Version: <1.0>Test Cases / 05-Jun-2011
Revision History
Date / Version / Description / Author05-Jun-2011 / <x.x> / <details> / <name>
Table of Contents
1.Introduction
1.1Definitions, Acronyms and Abbreviations
1.2References
2.Testing Environments
2.1Environment 1
2.2Environment 2
3.Setup Information (general Pre-conditions)
4.Test Cases
4.1Test Case 1: <Test Case Name>
4.1.1Description
4.1.2Pre-conditions for this test case
4.1.3Scenario
4.1.4Array of values
4.2Test Case 2: <Test Case Name>
1<Project name / Use Case> / Version: <1.0>
Test Cases / 05-Jun-2011
Test Cases
1.Introduction
[If necessary, write the introduction of the Test Cases. It should provide an overview of the entire document, and include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this set of Test Cases.]
1.1Definitions, Acronyms and Abbreviations
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to interpret properly the Test Cases. This information may be provided by the project Glossary.]
1.2References
[This subsection should provide a complete list of all documents referenced elsewhere in the Test Cases. Each document should be identified with a title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
1<Project name / Use Case> / Version: <1.0>
Test Cases / 05-Jun-2011
2.Testing Environments
2.1Environment 1
Machine Name / DB DirectoryVersion / DB / Client Server /Back-End
Tester Name / Test Date
New Log / If necessary, list the new log after tests have been run. / State / Successful/Failed
2.2Environment 2
[Repeat above chart as needed for environment 2.]
1<Project name / Use Case> / Version: <1.0>
Test Cases / 05-Jun-2011
3.Setup Information (general Pre-conditions)
[Enter the prerequisites to execute the test cases (e.g. Flags, parameters, etc.)]
1<Project name / Use Case> / Version: <1.0>
Test Cases / 05-Jun-2011
4.Test Cases
4.1Test Case 1: <Test Case Name>
4.1.1Description
[If necessary, write description text.]
4.1.2Pre-conditions for this test case
[If necessary, write pre-conditions text.]
4.1.3Scenario
Test CaseUC Step / Step Description / Expected Result / Actual Result
(if different from expected) / Successful/Failed / Environment Nbr (if failed) / Log Number (if failed)
Test Case Status / Successful/Failed
4.1.4Array of values
[If necessary, fill an array of value.]
Array of valuesScenario 1 / Scenario 2 / Scenario3 / Scenario 4 / Scenario 5
Value1
Value2
…
ValueX
Expected Result
Actual Result
(if different from expected)
Successful/Failed
Environment Nbr (if failed)
Log Number (if failed)
4.2Test Case 2: <Test Case Name>
[If necessary, repeat test case's previous section for each additional test case.]
1