<<Project Name>>

Test Specification and Test Cases

Customer Name
Directions for using template:
Read the Guidance (Arial blue font in brackets) to understand the information that
should be placed in each section of this template. Then delete the Guidance and
replace the placeholder within <<Begin tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
3453+5+3(-
2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues
discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO ARRANTIES! E"PRESS OR
IMP#IE$! IN T%IS $OC&MENT'
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
3453+5+3(-

Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title Test $pecification and Test 6ases
Author
6reation 1ate
8ast 9pdated
3453+5+3(-

Table of Contents
Test $pecification $ummar"............................................................................................
,nput $pecifications.........................................................................................................
:utput $pecifications......................................................................................................
Test ;n%ironment.............................................................................................................
$pecial 0rocedural Re<uirements...................................................................................-
,nter=case 1ependencies.................................................................................................-
Test 6ases.......................................................................................................................-
Test 6ase ,tem ) (......................................................................................................-
>eature A................................................................................................................?
>eature B................................................................................................................?
Test 6ase ( References...........................................................................................*
Test 6ase +..................................................................................................................*
>eature A................................................................................................................*
>eature B................................................................................................................@
Test 6ase + References...........................................................................................4
3453+5+3(-
%Introduction to t(e temp)ate
$escription* This Test #pecification is the technical outline for conducting the testing
process. &t defines the input, output, environment, and procedural guidelines at the
solution level as well as for each test case. The Test #pecification is developed using
the framework of the Test 'lan (created during the 'lanning 'hase) and the contents
of the functional specifications.
+ustification* Test specifications and test cases help to ensure that pro*ect teams
test the functions, features, and performance of solutions rigorousl and completel
with a minimum of ambiguit. Test specifications and test cases become the basis for
regression testing and evaluation when teams make changes necessar to correct
errors, improve performance, and meet new re+uirements.
,Team Ro)e Primar,* Test is responsible for the creation and deliver of the Test
#pecification and Test Case documents during the -evelopment phase.
$e-e)opment is instrumental in the review of the Test #pecification and Test Case
document to ensure testing covers all design elements.
Team Ro)e Secondar,* Pro.ram Mana.ement assists in removing barriers for Test
to complete all the ob*ectives defined in the test plans, and continues to manage
deliver in accordance to the schedule. Product Mana.ement needs to be aware of
test results to communicate the build status to e.ternal stakeholders. Re)ease
Mana.ement should be cogni/ant of test results that indicate an operational,
support and deploment environmental concerns that could *eopardi/e final deliver.
&ser E/perience should be aware of test results to ensure that user e.perience
re+uirements are being ade+uatel addressed throughout the test process.01
3453+5+3(- (

Test Specification Summar,
%$escription2 This section provides an overall summar of the contents of this
document.
+ustification2 Man readers, especiall the less technical pro*ect stakeholders, want
onl a general knowledge and understanding of the methods and tools a team
emplos to test a product, and this summar meets that need. The summar also
serves as an overview of the entire document.1
<<Begin tet here!!
Input Specifications
%$escription2 The &nput #pecifications section specifies the inputs needed to e.ecute
all the test cases for the solution. This ma include keboard, mouse, data files, or
other computer or user activities. The input should be described not onl b name but
also include attributes such as definitions, values, ranges, data structures, protocols,
interfaces, memor laout, databases, or files.
+ustification2 Teams test and evaluate solutions in an orderl manner, emploing
specific test cases to test the correctness of functions and to evaluate performance of
all kinds. Test cases consist of a well3defined input set that will produce
corresponding sets of e.pected output.1
<<Begin tet here!!
Output Specifications
%$escription2 The 4utput #pecifications section specifies the e.pected outputs from
this test. The output set should include data, timing information, screen messages,
logs, databases, memor structures, files, screens, etc. &n those cases in which an
actual test output can differ slightl from an e.pected output, include the range of
acceptabilit for the differences for each output.
+ustification2 5or each test input set, the pro*ect team has defined a corresponding
set of e.pected output. -efining, inspecting, and approving the output set prior to a
test enables the team to e.amine actual test results and +uickl determine if a test
was successful and in man cases to determine the cause of incorrect output.1
<<Begin tet here!!
Test En-ironment
%$escription2 The Test 6nvironment section describes the test environment7s
characteristics and configuration. This description should include hardware, software,
tools, other applications, etc. This description should be sufficientl complete so that
the test environment will produce results that ensure the solution will be successful in
its operational environment.
3453+5+3(- +

+ustification2 Testing re+uires a test environment that will produce the e.pected
results. &n man cases tests re+uire special test environments, and in other cases
tests can be conducted in operational environments. 8epeating tests re+uires
keeping as man test parameters, such as a test environment, constant. #oftware
inspections and pro*ect reviews alwas e.amine test environments. -ocumenting the
test environment makes this possible.1
<<Begin tet here!!
Specia) Procedura) Re0uirements
%$escription2 The #pecial 'rocedural 8e+uirements section describes an special
re+uirements to ensure that the test has integrit. This ma include setup processes,
restoring the environment to known baseline before and after test, and logging or
monitoring re+uirements.
+ustification2 Teams appl testing methods within prescribed testing procedures that
ma be uni+ue to test cases.1
<<Begin tet here!!
Inter1case $ependencies
%$escription2 The &nter3case -ependencies section identifies the dependencies that
e.ist among the test cases, showing which test cases must be performed first and
which follow.
+ustification2 Man functions depend upon input data produced as output from other
functions previousl tested. This section lists those test cases and identifies the test
input data each earlier test case provides to this test case.1
<<Begin tet here!!
Test Cases
%$escription2 The Test Cases section identifies ever uni+ue test case that will be
conducted. These ma be organi/ed b functions, features, and performance items
to be tested.
+ustification2 Teams test each function, each feature, and each performance
re+uirement defined b re+uirements and functional specifications. This section lists
the test items described in detail below.1
Test Case Item 1
%$escription2 The Test Case &tem 3 9 section identifies the testing item that is the
sub*ect of the test case.1
<<Begin tet here!!
3453+5+3(- .

Feature A
%$escription2 The 5eature A section briefl describes the overall feature and its
design.1
<<Begin tet here!!
Expected Behavior
%$escription* The 6.pected Behavior section describes the feature7s e.pected
behavior as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
behavior.1
<<Begin tet here!!
Expected Performance
%$escription* The 6.pected 'erformance section describes the feature7s e.pected
performance as intended b the re+uirements and design specifications. &t also
provides a definition of the range of acceptable differences between the e.pected
and actual performance.1
<<Begin tet here!!
Expected Reliability
%$escription* The 6.pected 8eliabilit section describes the feature7s e.pected
reliabilit as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
performance.1
<<Begin tet here!!
Additional NotesIss!es
%$escription* "se the Additional :otes$&ssues section for an additional information
that is not specified in the prior sections'1
<<Begin tet here!!
Feature 2
%$escription2 The 5eature B section briefl describes the overall feature and its
design.1
<<Begin tet here!!
Expected Behavior
%$escription* The 6.pected Behavior section describes the feature7s e.pected
behavior as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
behavior.1
<<Begin tet here!!
3453+5+3(- -

Expected Performance
%$escription* The 6.pected 'erformance section describes the feature7s e.pected
performance as intended b the re+uirements and design specifications. &t also
provides a definition of the range of acceptable differences between the e.pected
and actual performance.1
<<Begin tet here!!
Expected Reliability
%$escription* The 6.pected 8eliabilit section describes the feature7s e.pected
reliabilit as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
performance.1
<<Begin tet here!!
Additional NotesIss!es
%$escription* "se the Additional :otes$&ssues section for an additional information
that is not specified in the prior sections.1
<<Begin tet here!!
Test Case 3 References
%$escription2 The Test Case 9 8eferences section provides a traceabilit mechanism
from the re+uirements documents, functional specifications, and other documents
(user guides, operations guides, and installation guides) that were used to develop
the test case.1
<<Begin tet here!!
Test Case "
%$escription2 The Test Case 2 section identifies the testing item that is the sub*ect of
the test case.1
<<Begin tet here!!
Feature A
%$escription2 The 5eature A section briefl describes the overall feature and its
design.1
<<Begin tet here!!
Expected Behavior
%$escription* The 6.pected Behavior section describes the feature7s e.pected
behavior as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
behavior.1
3453+5+3(- ?

<<Begin tet here!!
Expected Performance
%$escription* The 6.pected 'erformance section describes the feature7s e.pected
performance as intended b the re+uirements and design specifications. &t also
provides a definition of the range of acceptable differences between the e.pected
and actual performance.1
<<Begin tet here!!
Expected Reliability
%$escription* The 6.pected 8eliabilit section describes the feature7s e.pected
reliabilit as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
performance.1
<<Begin tet here!!
Additional NotesIss!es
%$escription* "se the Additional :otes$&ssues section for an additional information
that is not specified in the prior sections.1
<<Begin tet here!!
Feature 2
%-escription2 The 5eature B section briefl describes the overall feature and its
design.1
<<Begin tet here!!
Expected Behavior
%$escription* The 6.pected Behavior section describes the feature7s e.pected
behavior as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
behavior.1
<<Begin tet here!!
Expected Performance
%$escription* The 6.pected 'erformance section describes the feature7s e.pected
performance as intended b the re+uirements and design specifications. &t also
provides a definition of the range of acceptable differences between the e.pected
and actual performance.1
<<Begin tet here!!
3453+5+3(- *

Expected Reliability
%$escription* The 6.pected 8eliabilit section describes the feature7s e.pected
reliabilit as intended b the re+uirements and design specifications. &t also provides
a definition of the range of acceptable differences between the e.pected and actual
performance.1
<<Begin tet here!!
Additional NotesIss!es
%$escription* "se the Additional :otes$&ssues section for an additional information
that is not specified in the prior sections.1
<<Begin tet here!!
Test Case 4 References
%$escription2 The Test Case 2 8eferences section provides a traceabilit mechanism
from the re+uirements documents, functional specifications, and other documents
(user guides, operations guides, and installation guides) that were used to develop
the test case.1
<<Begin tet here!!
3453+5+3(- @