<PROJECT NAME>

TEST CASE
Version <1.0>
<mm/dd/yyyy>
[Insert appropriate Disclaimer(s)]
<Project Name>
VERSION HISTORY
[Provide information on ho the development and distri!"tion of the Test Case#
"p to the final point of approval# as controlled and trac$ed. %se the ta!le !elo
to provide the version n"m!er# the a"thor implementin& the version# the date of
the version# the name of the person approvin& the version# the date that partic"lar
version as approved# and a !rief description of the reason for creatin& the
revised version.]
Version
#
Implemented
By
Revision
Date
Approved
By
Approval
Date
Reason
1.0 <'"thor name> <mm/dd/yy> <name> <mm/dd/yy> Test Case Template
draft
U Template Version! 12/31/07
Page 2 of 7
[Insert appropriate disclaimer(s)]
<Project Name>
Note to the Author
[(his doc"ment is a template of a Test Case doc"ment for a pro)ect. (he template
incl"des instr"ctions to the a"thor# !oilerplate te*t# and fields that sho"ld !e replaced
ith the val"es specific to the pro)ect.
+l"e italici,ed te*t enclosed in s-"are !rac$ets ([te*t]) provides instr"ctions to
the doc"ment a"thor# or descri!es the intent# ass"mptions and conte*t for
content incl"ded in this doc"ment.
+l"e italici,ed te*t enclosed in an&le !rac$ets (<te*t>) indicates a field that
sho"ld !e replaced ith information specific to a partic"lar pro)ect.
(e*t and ta!les in !lac$ are provided as !oilerplate e*amples of ordin& and
formats that may !e "sed or modified as appropriate to a specific pro)ect. (hese
are offered only as s"&&estions to assist in developin& pro)ect doc"ments. they
are not mandatory formats.
/hen "sin& this template for yo"r pro)ect doc"ment# it is recommended that yo" follo
these steps0
1. 1eplace all te*t enclosed in an&le !rac$ets (i.e.# <Pro)ect 2ame>) ith the
correct field val"es. (hese an&le !rac$ets appear in !oth the !ody of the
doc"ment and in headers and footers. (o c"stomi,e fields in 3icrosoft /ord
(hich display a &ray !ac$&ro"nd hen selected)0
a. 4elect 5ile>Properties>4"mmary and fill in the (itle field ith the
Doc"ment 2ame and the 4"!)ect field ith the Pro)ect 2ame.
!. 4elect 5ile>Properties>6"stom and fill in the 7ast 3odified# 4tat"s# and
8ersion fields ith the appropriate information for this doc"ment.
c. 'fter yo" clic$ 9: to close the dialo& !o*# "pdate the fields thro"&ho"t the
doc"ment ith these val"es !y selectin& ;dit>4elect 'll (or 6trl<') and
pressin& 5=. 9r yo" can "pdate an individ"al field !y clic$in& on it and
pressin& 5=. (his m"st !e done separately for >eaders and 5ooters.
?. 3odify !oilerplate te*t as appropriate to the specific pro)ect.
@. (o add any ne sections to the doc"ment# ens"re that the appropriate header
and !ody te*t styles are maintained. 4tyles "sed for the 4ection >eadin&s are
>eadin& 1# >eadin& ? and >eadin& @. 4tyle "sed for !oilerplate te*t is +ody
(e*t.
A. (o "pdate the (a!le of 6ontents# ri&ht<clic$ and select B%pdate fieldC and choose
the option< B%pdate entire ta!leC
D. +efore s"!mission of the first draft of this doc"ment# delete this B2otes to the
'"thorC pa&e and all instr"ctions to the a"thor# hich appear thro"&ho"t the
doc"ment as !l"e italici,ed te*t enclosed in s-"are !rac$ets.]
Page 3 of 7
[Insert appropriate disclaimer(s)]
<Project Name>
TAB"E O# CONTENTS
1 INTRODUCTION......................................................................................................................5
1.1 Purpose of The Test Case Document.................................................................................5
2 TEST CASE SPECIFICATION................................................................................................5
2.1 Description.........................................................................................................................5
2.2 Resources............................................................................................................................5
2.3 Preconditions......................................................................................................................5
2.4 Post Conditions...................................................................................................................5
2.5 Flow of Eents....................................................................................................................5
2.! "nclusion#E$clusion Points.................................................................................................5
2.% &pecial Re'uirements.........................................................................................................5
APPENDIX A: REFERENCES...................................................................................................6
APPENDIX B: KEY TERMS......................................................................................................7
Page 4 of 7
[Insert appropriate disclaimer(s)]
<Project Name>
$ INTRODUCTION
1.1 UROSE O# THE TEST CASE DOCU%ENT
[Provide the p"rpose of the (est 6ase Doc"ment. (his doc"ment sho"ld !e
tailored to fit a partic"lar pro)ectEs needs.]
The Test Case document documents the functional requirements of the <test case
title> test case. The intended audience is the proect manager! proect team! and
testing team. "ome portions of this document ma# on occasion $e shared %ith the
client/user and other sta&eholder %hose input/appro'al into the testing process is
needed.
& TEST CASE SECI#ICATION
[Descri!e the test case to !e performed]
2.1 DESCRITION
[Descri!e the test case and the individ"als involved in the testin&. Incl"de
dia&rams depictin& the interaction !eteen individ"als and the different elements
!ein& tested.]
2.2 RESOURCES
[Descri!e the individ"als involved in the testin&# their responsi!ilities# and their
association ith the test case.]
2.3 RECONDITIONS
[Descri!e the preconditions for the test case. ' precondition is the state of the
system that m"st e*ist !efore a test case can !e performed.]
2.4 OST CONDITIONS
[Descri!e the post conditions for the "se case. ' post condition is a list of possi!le
states the system can !e in immediately after a test case has finished.]
2.5 #"O' O# EVENTS
[Descri!e the flo of events that o"ld !e e*pected in normal conditions as ell
as any potential alternate flo of events# and e*ceptions/errors that may !e
e*pected.]
2.6 INC"USION(E)C"USION OINTS
[Descri!e other test cases that may !e incl"ded or e*cl"ded in the act of
e*ec"tin& this test case.]
2.7 SECIA" RE*UIRE%ENTS
[Descri!e any special re-"irements necessary to perform the test case.]
Page ( of 7
[Insert appropriate disclaimer(s)]
<Project Name>
Appendi+ A! Re,eren-es
[Insert the name# version n"m!er# description# and physical location of any
doc"ments referenced in this doc"ment. 'dd ros to the ta!le as necessary.]
The follo%ing ta$le summari)es the documents referenced in this document.
Do-.ment
Name and
Version
Des-ription "o-ation
<Doc"ment
2ame and
8ersion
2"m!er>
[Provide description of the
doc"ment]
<%17 or 2etor$ path here
doc"ment is located>
Page * of 7
[Insert appropriate disclaimer(s)]
<Project Name>
Appendi+ B! /ey Terms
[Insert terms and definitions "sed in this doc"ment. 'dd ros to the ta!le as
necessary. 5ollo the lin$ !elo to for definitions of pro)ect mana&ement terms
and acronyms "sed in this and other doc"ments.
http0//?.cdc.&ov/cdc"p/li!rary/other/help.htm
The follo%ing ta$le pro'ides definitions for terms rele'ant to this document.
Term De,inition
[Insert (erm] [Provide definition of the term "sed in this doc"ment.]
[Insert (erm] [Provide definition of the term "sed in this doc"ment.]
[Insert (erm] [Provide definition of the term "sed in this doc"ment.]
Page 7 of 7
[Insert appropriate disclaimer(s)]