Test Cases

Project Name
Revision 0.2

Test Cases - Rev 0.2

Project Name

Revision History
Version

Date

Reason For Changes

Prepared By

Reviewed by

0.1

12th August, 2013

Draft version/Template

Ravi. Ch

Vamshi. K

0.2

12th August, 2013

Added content at
Introduction & TC table

Vamshi. K

Uurmi Systems Confidential

2 of 9

Test Cases - Rev 0.2

Project Name

Table of Contents
1

INTRODUCTION ............................................................................................................................................ 5
1.1
1.2
1.3

SCOPE ................................................................................................................................................................5
TARGET AUDIENCE ...............................................................................................................................................5
REFERENCES ........................................................................................................................................................5

TEST PROCEDURE REQUIREMENT ................................................................................................................. 6

2.1
2.2

TEST SETUP .........................................................................................................................................................6

PRE-REQUISITES ...................................................................................................................................................6

TEST CASES ................................................................................................................................................... 7

GLOSSARY ..................................................................................................................................................... 8

Uurmi Systems Confidential

3 of 9

Test Cases - Rev 0.2

Project Name

Table of Figure
Figure 1.

Functional diagram ..................................................................................................... 6

Uurmi Systems Confidential

4 of 9

Test Cases - Rev 0.2

Project Name

1 Introduction
This document specifies the test cases for <module / system> testing of Project Name.
<<<Write about the project in a paragraph. >>>

1.1 Scope
<<<Explain what is covered in this document and what is not in the scope of this document>>>

1.2 Target Audience

<<< Who are the target audience. Module test case documents could be internal to the team
(depends upon the contract, if it is a customer project). The audience of sub-system test case
document can include integration team (who do complete system integration). And so on. >>>

1.3 References
<<< Based on the project and the scope of this document, the references may include
Specifications, Contract document, Statement of Work, SyRS, SRS, HRS, Design docs, Test plan,
test design & procedure documentation, etc.>>>

Uurmi Systems Confidential

5 of 9

Test Cases - Rev 0.2

Project Name

2 Test Procedure Requirement

<<<Note: If you have separate document explaining the test design & procedure, reference to
that here. Then, no need to explain about the test setup.>>>

2.1 Test Setup

<<<Simple functional diagram of the project / product should be displayed here. Replace the
below sample image. >>>

Figure 1.

Functional diagram

2.2 Pre-requisites
<<<Overall pre-requisites/conditions should be listed here, if any>>>
1.
2.
3.
4.

First pre-requisite
Second pre-requisite
Third pre-requisite
Fourth pre-requisite

Uurmi Systems Confidential

6 of 9

Test Cases - Rev 0.2

Project Name

3 Test Cases
<<< A test case in software engineering is a set of conditions or variables under which a quality
control engineer will determine whether an application or software system is working correctly
or not. >>>
<<<< Categorize test cases. The categorization of requirements in SyRS/SRS can be used as
reference. Create sub-sections, based on those categories >>>
Test Identifier
Test Name
Test Description
Requirements Addressed
Pre-requisite/condition
Test Input
Test Procedure
Test Result (Expected)
Post-condition (optional)

Uurmi Systems Confidential

PROJECTNAME_TC_MODULENAME_FUNCTIONALITY_1
<<< One line summary of test case, which may also be used as a
heading>>>
<<< Detailed description of the test case>>>
<<<The expected state of system and its environment, before this test
case is run >>>
<<<Steps involved in performing this test>>>
<<< It is something, that can be verified >>>
<<<The expected state of system and its environment, after this test case
is run. This specifies the things that need to be checked after the test has
been executed. >>>

7 of 9

Test Cases - Rev 0.2

Project Name

4 Glossary
<<< Acronyms and their full forms used in the test cases document should be displayed below.
Example acronyms are ;>>>
HRS - Hardware Requirement Specification
SRS -Software Requirement specifications
SyRS - System Requirement Specification
TC Test Cases

Uurmi Systems Confidential

8 of 9

Test Cases - Rev 0.2

Project Name

Last page of the Document

{Intentionally Left Blank}

Uurmi Systems Confidential

9 of 9