<<Project Name>>

Testing and Bug Report

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 MAKS NO !ARRANTIS" #PRSS OR
IMP$I%" IN T&IS %OC'MNT(
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 Testing and Bug Report
Author
6reation 1ate
8ast 9pdated
3453+5+3(-

Table of Contents
Test and Bug Reporting $ummar"..................................................................................
Test :ethods and Tools...................................................................................................
Testing :ethods $ummar"..........................................................................................
Test Tools $ummar"....................................................................................................
Test Report.......................................................................................................................
Test Results $ummar" ) 1eltas from 8ast Report.....................................................-
1iscrepancies in ;ecution of Test 0lan....................................................................-
Remaining Tests and Test 0lan Re%isions..................................................................-
Testing Areas..................................................................................................................-
0roduct Area (............................................................................................................-
Test Goal(s)............................................................................................................<
;%aluation 6riteria..................................................................................................<
Results....................................................................................................................<
Recommendations..................................................................................................<
0roduct Area +............................................................................................................<
Test Goal(s)............................................................................................................<
;%aluation 6riteria..................................................................................................*
Results....................................................................................................................*
Recommendations..................................................................................................*
Bug Reporting................................................................................................................*
Build $tatus................................................................................................................*
Bug Report..................................................................................................................*
Bug 6on%ergence Anal"sis.........................................................................................=
Re%ised Testing 0lan......................................................................................................=
3453+5+3(-
%Introduction to t)e Temp*ate
%escription+ The Testing and Bug &eport is a roll'up summar of the individual test
cases from each stage of testing. The intent is that this document will be used
multiple times at fre(uent intervals during the development, testing, and stabili)ation
phases. *or e+ample, during a si+'week build phase, the test team might submit this
report weekl, or si+ times during the build phase, however, the team might submit
the report bi'weekl during the stabili)ation phase.
,usti-ication+ -t is important to regularl communicate status of tests to the team and
other ke stakeholders, as test results ma impact plans and schedules..
/Team Ro*e Primar.+ Test is responsible for the deliver of the Testing and Bug
&eport during the 0evelopment and #tabili)ation phases. %e/e*opment is
instrumental in the review of the Test and Bug &eport in order to (ualif, (uantif, and
classif bugs in order to triage for resolution.
Team Ro*e Secondar.+ Program Management assists in removing barriers for Test
to complete all ob1ectives as defined in the test plans and monitors the progress
towards deliver in accordance to the schedule. Product Management needs to be
aware of test results to discuss the status of the build to e+ternal stakeholders.
Re*ease Management should be cogni)ant of test results to ensure that the test
harness represents true operational, support and deploment environmental
concerns that could 1eopardi)e final deliver. 'ser 0perience should be aware of
test results to confirm that test plans are ade(uatel e+ecuting against plan and that
user e+perience re(uirements are ade(uatel addressed throughout the test
phases.2.
3453+5+3(- (

Test and Bug Reporting Summar.
%%escription+ The Test and Bug &eporting #ummar section provides an overall
summar of the contents of this document.
,usti-ication+ #ome pro1ect participants ma need to know onl the highlights of the
plan, and summari)ing creates that user view. -t also enables the full reader to know
the essence of the document before the e+amine the details..
<<Begin tet here!!
Test Met)ods and Too*s
%%escription+ The Methods and Tools section is an analsis of actual testing that
occurred as compared against the Test 3lan. Avoid gross reiteration of the test plan '
address which elements of the plan were implemented successfull, but also address
where variations and deviations from plan occurred and wh..
Testing Methods Summary
%%escription+ The Testing Methods #ummar section lists and describes the test
methods emploed. -t should describe which methods were implemented
successfull, but also address where variations or deviations from the plan occurred
and wh.
,usti-ication+ This summar gives report readers some knowledge of the methods
the team emploed to develop and appl test cases, thus helping to assure them that
testing and evaluation was done in a rigorous and repeatable manner..
<<Begin tet here!!
Test Tools Summary
%%escription+ The Test Tools #ummar section lists and describes the test tools
emploed for each test method. -t should describe which tools were implemented
successfull, but also where variations or deviations from the plan occurred and wh.
,usti-ication+ This summar gives report readers some knowledge of the tools the
team applied to assist in the use of test methods, thus helping to assure them that
testing and evaluation was done efficientl and minimi)ed human error.
<<Begin tet here!!
Test Report
%%escription+ The Test &eport section provides a general solution'wide status report
of the actual test performed. This includes descriptions of what testing has occurred
since the last test report, an variations or deviations from the test plans,
identification of remaining test items, and an changes made to the test plan..
3453+5+3(- +

Test Results Summary Deltas from Last Report
%%escription+ The 4Test &esults #ummar section provides a summar recap of the
testing results since last report.
,usti-ication+ This summar helps to assure pro1ect stakeholders that the team is
following the original or the modified test plan..
<<Begin tet here!!
Discrepancies in Execution of Test Plan
%%escription+ The 0iscrepancies in 5+ecution of Test 3lan section identifies an
deviations against the test plan and test cases performed and provides a detailed
analsis of each deviation6s cause and 1ustification.
,usti-ication+ Testplans sometimes do not anticipate conditions and circumstances
that can affect actual performance. -n man cases a team must deviate from a test
plan and modif or create new and$or additional test cases to handle situations that
occur during testing..
<<Begin tet here!!
Remaining Tests and Test Plan Revisions
%%escription+ The &emaining Tests and Test 3lan &evisions section identifies the
test cases et to be used and identifies and describes an ke changes made to the
test plan since the last report.
,usti-ication+ This information ma impact the other team6s plans and schedules..
<<Begin tet here!!
Testing Areas
%%escription+ The Testing Areas section summari)es the results of the specific test
activities and results for each area of the solution.
,usti-ication+ 3ro1ect teams create test cases to test each product functional area
7specific tpes of calculations, creating lists, help, report creation, etc.8. -n man
cases, reporting the testing activities and results b functional area provides greater
meaning than reporting such information b individual re(uirements.
Product Area
%%escription+ The 3roduce Area 9 section describes the specific test activities and
results for this product area. :ou should change the heading of this section to the
name of the product area for better identification..
3453+5+3(- .

Test 1oa*2s3
%%escription+ The Test ;oal7s8 section restates what the test intends to accomplish,
for e+ample <verif compliance with standard =:>?..
<<Begin tet here!!
/a*uation Criteria
%%escription+ The 5valuation Criteria section identifies the criteria used to evaluate
the test cases..
<<Begin tet here!!
Resu*ts
4%escription+ The &esults section describes the results of running the test cases.
This ma be described as@
*unctionalit of product + dimension ) was validated
*eature A met or e+ceeded success criteria
A mean performance or peak load of > was achieved
#ignificant results includedA
-t ma be helpful to use graphics for load testing 7i.e. screen shots of 3erfmon, etc.8..
<<Begin tet here!!
Recommendations
%%escription@ The &ecommendations section identifies and describes critical feature
deficiencies and makes recommendations for alteration, elimination,
e+pansion$reduction of the feature..
<<Begin tet here!!
Product Area !
%%escription+ The 3roduct Area 2 section describes the specific test activities and
results for this product area. :ou should change the heading of this section to the
name of the product area for better identification..
Test 1oa*2s3
%%escription+ The Test ;oal7s8 section restates what the test intends to accomplish,
for e+ample <verif compliance with standard =:>?..
<<Begin tet here!!
3453+5+3(- -

/a*uation Criteria
%%escription+ The 5valuation Criteria section identifies the criteria used to evaluate
the test cases..
<<Begin tet here!!
Resu*ts
4%escription+ The &esults section describes the results of running the test cases.
This ma be described as@
*unctionalit of product + dimension ) was validated
*eature A met or e+ceeded success criteria
A mean performance or peak load of > was achieved
#ignificant results includedA
-t ma be helpful to use graphics for load testing 7i.e. screen shots of 3erfmon, etc.8..
<<Begin tet here!!
Recommendations
%%escription@ The &ecommendations section identifies and describes critical feature
deficiencies and makes recommendations for alteration, elimination,
e+pansion$reduction of the feature..
<<Begin tet here!!
Bug Reporting
%%escription+ The Bug &eporting section describes the general status of the build
and provides details on bugs.
,usti-ication@ This information assists the team in understanding if the pro1ect
schedule is on track..
"uild Status
%%escription+ The Build #tatus section describes the stabilit of the build and where
in the milestone process the test team believes the current state of the build lives..
<<Begin tet here!!
"ug Report
%%escription+ The Bug &eport section identifies all outstanding bugs and their
status. :ou ma provide this information in a matri+ or listing. :ou ma choose to
utili)e an attached tool or spreadsheet or embed visuals into this section report. Bink
each bug to the test case from which the bug was identified, and using a traceabilit
link, to the area7s8 of the solution affected..
3453+5+3(- <

<<Begin tet here!!
"ug #onvergence Analysis
%%escription+ The Bug Convergence Analsis section describes the specific point in
the build process where the number bugs resolved e+ceeds the number of new bugs
reported. This is a critical 1uncture in the stabili)ation phase that indicates an
important milestone in the march to final ship. *rom this point, build status should be
anal)ed and measured criticall in order to be able to estimate reliabl when the
deliver is approaching a shipping status..
<<Begin tet here!!
Re/ised Testing P*an
%%escription+ The &evised Testing 3lan section is a submission of the revised test
plan, making appropriate modifications to reflect new test plans and an changes to
goals, criteria, bug'triage strategies, and test cases.
,usti-ication+ #ince testing is a critical element in the deliver of a successful
solution, the test plan must alwas reflect what is actuall being done towards this
goal..
<<Begin tet here!!
3453+5+3(- *