Acceptance Test Plan

Template
Approved By:
____________________________ ___________________________
(Title) (Title)
CURRENT DOCUMENT STATUS
Version Number
File Name
Delivery Dae
O!ner
Des"ripion
REV#S#ON $#STOR%
Revision Version Des"ripion o& C'an(e C'an(ed By E&&e"ive Dae
TAB)E OF CONTENTS
1 INTRODUCTION.......................................................................................................1
2 ACCEPTANCE TEST APPROACH...........................................................................1
3 ACCEPTANCE TEST PROCESS...............................................................................1
3.1 Establish Acceptace Test !"a#e$%"&....................................................................1
3.2 Pla Acceptace Test Acti'ities...............................................................................1
3.3 De'el%p Acceptace Test Cases...............................................................................2
3.3.1 S%("ces )%" Test Cases.....................................................................................2
3.3.2 St"(ct("e )%" Acceptace Test..........................................................................2
3.3.3 Test P"%ce*("es De'el%p#et.........................................................................3
3.3.+ Testi, P"i%"it-................................................................................................3
3.3.. Test T%%ls.........................................................................................................3
3.3./ Acceptace Test 0ate"ials...............................................................................3
3.3.1 De'el%p Test T"aceabilit- D%c(#etati%.......................................................3
3.+ Set Up the Acceptace Testi, E'i"%#et...........................................................+
3.+.1 E'i"%#et P"epa"ati%.................................................................................+
3.+.2 Ha"*$a"e2S%)t$a"e..........................................................................................+
3.. C%*(ct Acceptace Test Rea*iess Re'ie$ (ATRR).............................................+
3./ E3ec(te Tests............................................................................................................
3./.1 Rec%"* Iss(es2De)ects.......................................................................................
3./.2 Retesti, C%""ecte* S%)t$a"e........................................................................../
3./.3 Acceptace Re,"essi% Testi,......................................................................./
3./.+ D%c(#et Acceptace Test Res(lts................................................................./
3.1 C%*(ct Acceptace Test Stat(s 0eeti,s............................................................../
3.4 Acceptace Test Deli'e"ables..................................................................................1
3.5 S(pp%"t Cliet Acceptace......................................................................................1
+ ACCEPTANCE TEST ENTRANCE 2 E6IT CRITERIA...........................................1
+.1 Acceptace Test Et"ace C"ite"ia...........................................................................1
+.2 Acceptace Test E3it C"ite"ia..................................................................................1
. REPORTS....................................................................................................................4
..1 Ite"i# Stat(s Rep%"ti,..........................................................................................4
..2 Iss(e2De)ect Rep%"ti,............................................................................................5
..3 Acceptace Test S(##a"- Rep%"t.........................................................................17
..+ Acceptace Test !ial Rep%"t................................................................................12
/ RIS8S........................................................................................................................13
APPENDICES...................................................................................................................1+
APPENDI6 A 9 ACRON:0 ;IST...................................................................................1+
)is o& E*'ibis
E3hibit 1< Sa#ple Acceptace Test Sche*(le......................................................................2
E3hibit 2< Sa#ple Ite"i# Stat(s Rep%"t.............................................................................4
E3hibit 3< Iss(e2De)ect Rep%"t Sa#ple................................................................................5
E3hibit +< Sa#ple Acceptace Test S(##a"- Rep%"t.......................................................11
E3hibit .< Acceptace Test !ial Rep%"t Sa#ple..............................................................12
E3hibit /< Acceptace Test Pla Te#plate O(tlie............................................................1.
+ #NTRODUCT#ON
Desc"ibe the *%c(#et sc%pe. S(##a"i=e s-ste# )(cti%alit-. P"%'i*e the s-ste# a#e
a* bac&,"%(* i)%"#ati%. ;ist "e)e"eces> icl(*i, *%c(#etati% that p"%'i*es
s(pple#etal i)%"#ati%.?
This document is the Acceptance Test Plan (ATP) for <system name> software. The
acceptance test verifies that the system works as required and validates that the correct
functionality has been delivered. The ATP establishes the acceptance test framework
used by the acceptance test team to plan e!ecute and document acceptance testin". #t
describes the scope of the work performed and the approach taken to e!ecute the tests
created to validate that the system performs as required. The details of the ATP are
developed accordin" to the requirements specifications and must show traceability back
to those specifications.
, ACCE-TANCE TEST A--ROAC$
@Desc"ibe the test app"%ach ch%se )%" the acceptace test e))%"t. P"%'i*e a %'e"'ie$
that c%'e"s the a*'ata,es %) (si, this app"%ach a* $h- it $as selecte*.?
. ACCE-TANCE TEST -ROCESS
@Desc"ibe the plai,> *esi,> e3ec(ti%> a* *%c(#etati% ass%ciate* $ith the
acceptace test e))%"t i the )%ll%$i, s(bsecti%s. ;ist the #aA%" acceptace test
acti'ities.?
./+ Esablis' A""epan"e Tes Frame!or0
@Desc"ibe h%$ the ATP is (se* i establishi, the Acceptace Test )"a#e$%"&. Desc"ibe
the steps the acceptace test tea# (ses t% establish the acceptace test p"%cess> a*
i*eti)- the "ele'at ip(ts> %(tp(ts> a* p"%cess c%t"%ls.?
The Acceptance Test Plan establishes the acceptance test framework used by the to plan
e!ecute and document acceptance testin" of <system or software>. #ndustry best
practices for acceptance testin" and data derived from the acceptance test team$s
interface with the software development processes as well as <name any standards used
by the or"ani%ation> form the basis for the AT framework.
./, -lan A""epan"e Tes A"iviies
@Desc"ibe the %'e"all pla )%" acceptace test acti'ities> icl(*i, i*eti)icati% %) the
testi, tas&s a* the sche*(le )%" acc%#plishi, th%se tas&s. A sche*(le %(tlii, the
plae* acceptace test acti'ities a* the aticipate* ti#elie )%" th%se acti'ities sh%(l*
als% be p"%'i*e*. The sche*(le ca be sta* al%e as sh%$ i E3hibit 1> %" ite,"ate*
it% a la",e" B%"& C"ea&*%$ St"(ct("e (BCS).?
A successful acceptance test effort requires plannnin". The acceptance test team
identifies the tasks that need to be accomplished includin" milestones. The functional
requirements and <or"ani%ation&name> documents are the primary drivers for
identifyin" those tasks.
The acceptance test schedule is the timeline of acceptance testin" activities and
deliverable due dates. 'or each acceptance testin" effort a test schedule is developed
identifyin" the ma(or test preparation test e!ecution and test reportin" activities as well
as providin" interim checkpoints to measure the pro"ress of acceptance testin". The
<client&other name(s)> monitors the acceptance test effort.
E*'ibi +: Sample A""epan"e Tes S"'edule
Activity
Planned
Completion
Date
Actual
Completion
Date
Deliverable/
Checkpoint
Plan Acceptance Testin" for <system )*>
Preliminary Acceptance Test +chedule
#dentify Test ,aterials
Preliminary Acceptance Test ,atri!
-stablish Acceptance Test -nvironment
Acceptance Test -nvironment
#nventory
.onduct Acceptance Test /eadiness
/eview
0raft Acceptance Test Plan ,atri!
.ompleted Test /eadiness /eview
.hecklist
-!ecute Tests Acceptance Test Pro"ress
.omplete Acceptance Testin" Acceptance Test +ummary /eport
0ocument Acceptance Testin" 'inal Acceptance Test /eport
./. Develop A""epan"e Tes Cases
@I the )%ll%$i, s(bsecti%s> *esc"ibe the p"%cess (se* t% c"eate acceptace test cases.
De)ie the test cases i the acceptace test e))%"t.?
././+ Sour"es &or Tes Cases
@I*eti)- the s%("ces %) s-ste# i)%"#ati% that se"'e as the basis a* "e)e"ece )%" the
test cases. E3a#ples icl(*e the !RD> #a(als> ite"'ie$s> *esi, *%c(#ets %" act(al
s-ste# c%*e.?
The acceptance test team uses the requirements e!istin" documentation interviews
research and actual e!ecution of the e!istin" test software to aid in development of the
acceptance test cases. The acceptance test team reviews the software documentation
other documentation and e!istin" software to identify software components and features.
The acceptance test team also attends requirements and desi"n meetin"s and interviews
persons involved in the system analysis development test and operations to identify
"aps and clarify questions.
././, Sru"ure &or A""epan"e Tes
@Desc"ibe the app"%ach (se* t% st"(ct("e a* %",ai=e the test cases. Desc"ibe test case
,"%(pi,s (s(ch as )(cti%al> s-ste# a* s%)t$a"e). Als%> p"%'i*e a *esc"ipti% %) the
testi, cate,%"ies $ithi each test case ,"%(pi, (s(ch as a'i,ati%al> ite")ace> etc).?
.omprehensive acceptance test materials are a critical component of a successful
acceptance test pro"ram. The acceptance test team uses a requirements1driven
structured approach to identify acceptance test data.
././. Tes -ro"edures Developmen
@P"%'i*e a *esc"ipti% %) the test p"%ce*("es (se* )%" acceptace testi, a* h%$ the test
p"%ce*("es a"e c"eate*.?
Test procedures provide the testers with precise steps that should be followed to e!ecute a
test. Test procedures are essentially the recipe used to perform the test. Test cases are
identified and documented as pro"ressively detailed modules.
././1 Tesin( -rioriy
@Disc(ss h%$ c"itical c%#p%ets $ill be p"i%"iti=e* )%" a ,i'e acceptace test a* the
alte"ati'es that a"e a'ailable t% c%#pesate )%" a- sche*(le a*A(st#ets.?
Assi"nin" a test priority provides built in miti"ation for schedule risks. Therefore prior
to the test effort the most critical system features are identified and assi"ned a priority
level. The most critical items are tested first followed by pro"ressively less critical
items. This ensures the critical items are tested when insufficient test time is allocated for
acceptance testin". This approach also provides immediate feedback on the critical
system features early in the acceptance test so the developers can be"in addressin"
serious defects immediately. Any test cases and system features that are not tested are
documented and provided in the Acceptance Test +ummary /eport.
././2 Tes Tools
@;ist a* *esc"ibe the test t%%ls that $ill be (se* )%" the acceptace test e))%"t. I*eti)-
each t%%l> h%$ it $ill be (tili=e*> a* the bee)it %) (si, that pa"tic(la" t%%l.?
././3 A""epan"e Tes Maerials
@P"%'i*e a list %) the acceptace test #ate"ials> a* i*eti)- $he"e the #ate"ials a"e
l%cate* $ithi the acceptace test pla. These #ate"ials #a- icl(*e ite#s s(ch as the
act(al test case a* p"%ce*("es.?
As the acceptance test activities are performed acceptance test plan materials are
created and added to the acceptance test plan as appendices. -ach test for a particular
release has its own correspondin" appendi! which is continously updated throu"hout the
acceptance test.
././4 Develop Tes Tra"eabiliy Do"umenaion
@De"i)- the s-ste#s "eE(i"e#ets ha'e bee #et b- *e'el%pi, the t"aceabilit-. Sh%$
h%$ the test acti'ities #ap t% each %) the i*i'i*(al s-ste# "eE(i"e#ets.?
Test traceability is used to verify that functional requirements are accounted for and
tested in the delivered software. #t provides traceability between the requirements and
the test materials. The acceptance test team develops the traceability from the baselined
requirements documents for the software.
./1 Se Up 'e A""epan"e Tesin( Environmen
@Desc"ibe the acceptace test e'i"%#et a* p"%'i*e i)%"#ati% % the ha"*$a"e> a*
the s%)t$a"e ee*e* t% e3ec(te the acceptace testi,.?
The acceptance test environment is not baselined until after the Acceptance Test
/eadiness /eview (AT//). The AT// enables the acceptance test team the
stakeholders and the system support contractors to identify and address missin" or
incorrectly confi"ured hardware and software components.
./1/+ Environmen -reparaion
@P"%'i*e a b"ie) *esc"ipti% %) the acceptace test e'i"%#et a* h%$ the e'i"%#et
$ill be establishe*. Disc(ss the app"%ach the tea# $ill ta&e t% es("e the test e'i"%#et
is cl%sel- #atche* t% the p"%*(cti% e'i"%#et.?
#n preparation for acceptance testin" the acceptance test team identifies and addresses
missin" or incorrectly confi"ured hardware and software components. A pre1tested
acceptance test environment facilitates the ability to be"in acceptance testin"
immediately after the AT//.
Preparatory activities involve constructin" the actual acceptance test environment and
installin" the hardware and software includin" the software to be tested in order to
ensure the confi"uration is correct. .han"es need to be closely mana"ed and controlled.
Prior to an installation or confi"uration the acceptance test team reviews a list of
affected components and the planned installation or confi"uration activities. 0eviations
from the planned activities are recorded and reported to the acceptance test team. The
acceptance test team be"ins acceptance testin" by conductin" an initial series of ad hoc
dia"nostic tests desi"ned to e!ercise the acceptance test environment and verify that
ma(or system software capabilities are available and functionin".
./1/, $ard!are5So&!are
@;ist the t-pes a* E(atities %) ha"*$a"e "eE(i"e* al%, $ith the c%)i,("ati%. P"%'i*e
a list %) the s%)t$a"e ee*e* t% s(pp%"t the s-ste# test that is %t pa"t %) the s%)t$a"e
bei, teste*. This sh%(l* icl(*e a- s(pple#etal s-ste# s%)t$a"e t% be (se* $ith the
e$ s%)t$a"e t% es("e c%#patibilit-. A- s%)t$a"e "eE(i"e* t% "ec%"* test "es(lts> s(ch as
test a(t%#ati% s%)t$a"e> sh%(l* als% be icl(*e*.?
./2 Condu" A""epan"e Tes Readiness Revie! 6ATRR7
@E3plai the p"%cess ass%ciate* $ith c%*(cti, a ATRR. Icl(*e a list %) c"ite"ia that
#(st be satis)ie* i %"*e" t% p"%cee* $ith Acceptace Testi,.?
The AT// is a critical acceptance testin" checkpoint. At this review <name> the
acceptance test team and <developer or contractor> (ointly review the status of the
+ystem Test results and known problems the developed system and its associated
documentation the planned acceptance testin" the acceptance test environment and the
support environment to determine whether or not to be"in acceptance testin". 2ith the
Acceptance Test Plan as the "uidin" document components reviewed include but are not
limited to3
+oftware components
0atabase
-nvironmental components
0ocumentation
4nown problems and outstandin" issues from the +ystem Test
#nventory of the acceptance test environment
#f the status of one or more of the components is unsatisfactory the parties identify
corrective actions and schedule another AT//. #f the status is acceptable then testin"
will proceed.
./3 E*e"ue Tess
@Desc"ibe the acti'ities ass%ciate* $ith the act(al e3ec(ti% %) the acceptace test. This
icl(*es *e)ect "ec%"*i, a* t"ac&i,> testi, %) e$ s%)t$a"e "eleases> "e,"essi%
testi,> a* *%c(#eti, the test "es(lts.?
Acceptance test e!ecution is an iterative process that be"ins with the initial e!ecution of
the planned tests. #f no defects are discovered then the test procedure has 5passed.6 #f
defects are discovered they are documented (ointly dispositioned by the ..7 corrected
and retested.
#deally acceptance testin" continues until all the acceptance tests are successfully
e!ecuted. 8owever the acceptance test team reco"ni%es that the system has firm
deadlines. Thus early in acceptance testin" the acceptance test team focuses on critical
functionality and new features. #f test time e!pires before completion of the acceptance
tests the acceptance test team provides the <client> with a list of the untested tests alon"
with a risk analysis re"ardin" the untested functionality.
./3/+ Re"ord #ssues5De&e"s
@Desc"ibe the %'e"all p"%cess )%" "ec%"*i, a* t"ac&i, *e)ects %" iss(es )%(* *("i,
acceptace testi,. A**iti%all-> p"%'i*e a *esc"ipti% )%" the S%)t$a"e Cha,e ReE(est
(SCR) p"%cess> icl(*i, h%$ the- a"e s(b#itte*> #%it%"e*> "ep%"te* a* cl%se* (%"
p"%'i*e "e)e"ece).?
As the acceptance test team identifies issues and defects the acceptance test team
records them. 'or each incident the defect trackin" system documents what occurred
how it occurred when it occurred the tester who discovered it what system baseline was
bein" used and a preliminary assessment of the severity. At a"reed upon intervals the
..7 meets to review the identified incidents and a"ree upon their prioriti%ation and
disposition. 'or severe errors the parties may conduct a more immediate emer"ency
meetin". The acceptance test team tracks and reports on open defects until they are
closed.
./3/, Reesin( Corre"ed So&!are
@P"%'i*e a %'e"'ie$ % h%$ the acceptace test tea# ha*les s%)t$a"e patches.
Desc"ibe the steps that a"e )%ll%$e* t% the "etest s%)t$a"e that is #%*i)ie* *("i, the
acceptace test phase %" has a**iti%al patches c%taii, s%)t$a"e )i3es.?
To control the acceptance test environment the acceptance test team accepts software
and patches containin" issue and defect resolutions at mutually a"reed upon intervals
durin" the acceptance test e!ecution. Accompanyin" the software correction the
acceptance test team recieves an inventory of chan"ed components the defects corrected
evidence of unit and&or +ystem Testin" and instructions for installin" the correction.
9pon receipt of a software correction the acceptance test team re1e!ecutes acceptance
test procedures to retest each corrected defect. #f the incident does not re1occur the
acceptance test team recommends closure of the defect at the ne!t incident review
meetin". #f the incident continues to occur the acceptance test team informs the <client>
and the development team and the defect remains open.
./3/. A""epan"e Re(ression Tesin(
@E3plai the app"%ach that $ill be a*%pte* )%" "e,"essi% testi,. Disc(ss h%$ "e,"essi%
testi, $ill be p"i%"iti=e* a* tail%"e* t% )it ti#e2"es%("ce c%st"aits.?
After receipt of a software correction the acceptance test team performs re"ression
testin" to ensure the defect or issue has been reolved and previously workin" software is
not impacted. Priorities for re"ression testin" are assi"ned based on function criticality
time and available resources.
./3/1 Do"umen A""epan"e Tes Resuls
@I*eti)- the acti'ities "elate* t% acceptace test "es(lts *%c(#etati%> a* i*eti)- the
"ep%"ts that $ill be p"%*(ce* t% *%c(#et the acceptace test "es(lts.?
At the end of the acceptance test the acceptance test team produces two reports
summari%in" the results of the acceptance test. The Test +ummary /eport is a short
report summari%in" the test activities and identifies outstandin" deficiencies and issues.
The acceptance test team delivers this report on a mutually a"reed upon timeframe
shortly after the end of acceptance test. This report provides the <client> with
information to make an informed system software acceptance or re(ection decision.
The Acceptance Test 'inal /eport is the detailed record of the acceptance test activities.
#t records which tests were performed the pass&fail status of each test and the
discrepancies or issues found. #n addition the Acceptance Test 'inal/eport identifies
new tests added to the planned tests. The Acceptance Test /eport is delivered as part of
the appendi! to the 'inal Acceptance Test on a mutually a"reed upon date at the
conclusion of acceptance testin".
./4 Condu" A""epan"e Tes Saus Meein(s
@P"%'i*e the c"ite"ia )%" h%l*i, stat(s #eeti,s a* i*eti)- $h% $ill atte* the
#eeti,s.?
The <client> acceptance test and development contractor will meet periodically to
discuss the status of acceptance testin". This will ensure any ma(or issues or defects are
identified in a timely manner so they can be resolved.
./8 A""epan"e Tes Deliverables
@;ist the *eli'e"ables that $ill be p"%'i*e* at the c%cl(si% %) acceptace testi,.?
The followin" is a list of deliverables produced durin" the acceptance test phase3
Acceptance Test Plan
Acceptance Test +chedule
Traceability
Acceptance Test -nvironment #nventory
Acceptance Test +ummary /eport
Acceptance Test 'inal /eport
./9 Suppor Clien A""epan"e
@P"%'i*e a %'e"'ie$ %) Acceptace Test acti'ities a*%pte* b- the acceptace test tea# t%
s(pp%"t the FclietGsH *ecisi%9#a&i, p"%cess "elate* t% s-ste# acceptace.?
The <client> is the stakeholder who determines whether to accept or re(ect the delivered
software. Acceptance testin" e!ercises the software and provides data to be used in that
decision. The <client> uses the acceptance test results from the Acceptance Test
+ummary /eport to determine whether the software as1built fulfills the <client$s>
mission requirements. #f the <client> determines that the software fulfills the
requirements the <client> accepts the software and the system is prepared for
production. #f the <client> determines that the software does not fulfill its requirements
the <client> makes a determination on further action.
1 ACCE-TANCE TEST ENTRANCE 5 E:#T CR#TER#A
1/+ A""epan"e Tes Enran"e Crieria
@P"%'i*e a list %) the et"ace c"ite"ia that #(st be #et p"i%" t% the %set %) acceptace
testi,.?
The Acceptance Test /eadiness /eview must be completed with the followin" minimum
entrance criteria.
A. Acceptance Test Plan updated with the current tests
7. .ompleted +ystem Test /eport
.. Any open system issues.
1/, A""epan"e Tes E*i Crieria
@P"%'i*e a list %) the e3it c"ite"ia that #(st be #et )%" acceptace testi, t% )%"#all- e*.?
Acceptance Test -!it is based on the followin" criteria3
A. Acceptance test team preparation of the Acceptance Test +ummary /eport that
reports the initial e!ecution results of the acceptance testin".
7. .ompletion of the Acceptance Test 'inal /eport which provides the final status of
acceptance test activities for a specific release.
2 RE-ORTS
@P"%'i*e a list a* *esc"ipti% %) all the acceptace test "ep%"ts ,ee"ate* *("i, the
acceptace testi, p"%cess. I*eti)- $he the "ep%"t $ill be p"%*(ce*> the )"eE(ec- )%"
each "ep%"t> a* the a'ailable )%"#at(s).
2/+ #nerim Saus Reporin(
@Disc(ss a- a* h%c "ep%"ti, capabilities that a"e a'ailable %'e" the c%("se %) the
acceptace testi,.?
E*'ibi ,: Sample #nerim Saus Repor
INTERIM TEST STATUS REPORT
Tester Names: Date:
Functional Areas
Number of
tests
executed
Subtotal of
tests
passed
Subtotal of
tests failed
Percent
Failed
Number of
tests not
tested
Functional Area 1
Functional Area 2
Functional Area 3
Functional Area 4
2/, #ssue5De&e" Reporin(
@Desc"ibe the iss(e p"%ble# "ep%"ti, p"%cess. I) a'ailable> "e)e" t% p"%ble# "ep%"ti,
p"%ce*("es *%c(#etati%. Als%> i*eti)- a- p"%ble# "ep%"ti, t%%ls bei, (se*. A
sa#ple "ep%"t )%"#at is p"%'i*e* i E3hibit 3> h%$e'e" a alte"ati'e )%"#at ,ee"ate*
)"%# a t%%l #a- be s(bstit(te*. P"%'i*e a list %) the p"%ble# t-pes a* thei" *esc"ipti%.
The test p"%ble# "ep%"ti, p"%cess icl(*es<
I*eti)-i, the p"%ble#
C"eati, the s%)t$a"e cha,e "eE(est (SCR)
Assi,i, a p"%ble# stat(s a* se'e"it-
0%it%"i, the SCR "es%l(ti%
De"i)-i, the "es(lts
Cl%si, "es%l'e* SCRs
SCR stat(s?
E*'ibi .: #ssue5De&e" Repor Sample
ISSUE/DEFECT REPORT
Tester Name: Software Version:
Area of Software
Impacted:
Preliminary Severity
Assessment:
Nature of Issue/Defect:
What occurred:
How did it occur:
When did it occur:
Descrie how to
reproduce the error:
SCR INFORMATION
Assi!ned S"# Numer: Severity: Status:
2/. A""epan"e Tes Summary Repor
@Desc"ibe the c%tets %) the Acceptace Test S(##a"- Rep%"t. The acceptace test
tea# $ill *eli'e" the Acceptace Test S(##a"- Rep%"t % late" tha a a,"ee* (p%
(#be" %) *a-s a)te" the e* %) acceptace testi,. This "ep%"t p"%'i*es the cliet $ith
the i)%"#ati% t% )%"#(late a IacceptJ %" I"eAectJ *ecisi%. The i)%"#ati% $ithi the
"ep%"t icl(*es<
T%tal (#be" %) tests
S(bt%tal (#be" %) tests e3ec(te*
S(bt%tal %) (#be" passe*
S(bt%tal %) (#be" )aile*
Se'e"it- %) )aile* test iss(es ,"%(pe* b- l%$> #e*i(#> %" hi,h
S(bt%tal %) (#be" %t teste*
S(bt%tal %) tests % l%,e" applicable
T%tal (#be" %) SCRs
N(#be" %) Ope SCRs
N(#be" %) SCRs %t teste*
N(#be" %) ("es%l'e* SCRs
N(#be" %) SCRs )aile*
N(#be" %) SCRs "es%l'e* a* teste*
N(#be" %) Cl%se* SCRs
S(bt%tal b- le'el a* %pe2cl%se* stat(s
N(#be" %) s%)t$a"e *eli'e"ies *("i, testi,?
E*'ibi 1: Sample A""epan"e Tes Summary Repor
ACCEPTANCE TEST SUMMARY REPORT
Functional Areas
Total
Number of
Tests
Number of
tests
executed
Percent
Complete
Subtotal
of tests
passed
Subtotal of
tests failed
Percent
Failed
Number of
tests not
tested
Total of
tests no
longer
applicable
Functional
Area 1
1418 1265 89.21% 1137 20 1.58% 148 5
Functional
Area 2
2277 1062 46.64% 1055 17 1.60% 1213 2
Functional
Area 3
845 834 98.70% 778 12 1.44% 10 1
Functional
Area 4
455 450 98.90% 412 8 1.78% 5 0
SCR Informaton
Total
Numer
S"#s
Numer of
"losed
S"#s
Numer of
$pen
S"#s
Numer of
S"#s Not
Tested
Numer of
%nresolved
S"#s
Numer of
S"#s &ailed
Numer of
S"#s
#esolved and
Tested
+;; 23 11 9 +3 4 +,
2/1 A""epan"e Tes Final Repor
@Desc"ibe the c%tets %) the Acceptace Test !ial Rep%"t. The Acceptace Test !ial Rep%"t is
the *etaile* "ec%"* %) acceptace test acti'ities. The testi, pe")%"#e*> the pass2)ail stat(s %)
each test case> a* *isc"epacies %" iss(es )%(* a"e "ec%"*e*. At a #ii#(#> the Acceptace
Test !ial Rep%"t icl(*es<
S-ste# a#e
Kee"al *esc"ipti% %) the s-ste# test e))%"t
Details )%" each test al%, $ith t"aceabilit- t% the "eE(i"e#ets
Acceptace teste" a#es a* *ates
;ist %) ("es%l'e* s%)t$a"e *e)ects a* iss(es a* thei" e))ects % the s-ste#> #iti,ati%
%) the "is&s> %" $%"&9a"%(*s?
E*'ibi 2: A""epan"e Tes Final Repor Sample
ACCEPTANCE TEST FINA! REPORT
System Name: Date:
General description of the acceptance test effort:
Unresol"e# Defects
ssue!Defect
mpact
"#$ %$ &'
(is)
%itigation
"f )no*n'
+or) Around
"f )no*n'
3 R#S<S
@P"%'i*e a list %) the s-ste# test "is&s )"%# the p"%AectGs Ris& 0aa,e#et Pla a* the p%ssible
#iti,ati% )%" th%se "is&s. These "is&s ca be icl(*e* as a sepa"ate secti% i this *%c(#et> %"
"e)e"ece* as past %) the Ris& 0aa,e#et Pla.?
The followin" are typical "eneral overall acceptance test risks3
:. #nsufficient test time ;
/isk3 #f the amount of time available is too short the acceptance test team may not
have enou"h time to complete acceptance testin" or perform re"ression testin".
,iti"ation3 0evelop a critical path of tests prioriti%ed by importance.
<. #ncomplete requirements 1
/isk3 ,ay result in insufficient testin" of the system.
,iti"ation3 9se the traceability matrices to track the testin"&requirements
relationship.
=. A test environment that is not the same as the production environment 1
/isk3 ,ay prevent the detection of some defects and issues.
,iti"ation3 *ote the differences and work to have them as close as possible.
A--END#CES
A--END#: A = ACRON%M )#ST
E*'ibi 3: A""epan"e Tes -lan Templae Ouline
ACCE-TANCE TEST -)AN TEM-)ATE
Cover -a(e
Table o& Conens
+ #NTRODUCT#ON
, ACCE-TANCE TEST A-ROAC$
. ACCE-TANCE TEST -ROCESS
3.1 Establish Acceptace Test !"a#e$%"&
3.2 Pla Acceptace Test Acti'ities
3.3 De'el%p Acceptace Test Cases
3.3.1 S%("ces )%" Test Cases
3.3.2 St"(ct("e )%" Acceptace Test
3.3.3 Test P"%ce*("es De'el%p#et
3.3.+ Testi, P"i%"it- (Test T"ia,e)
3.3.. Use %) the Test T%%l
3.3./ Acceptace Test 0ate"ials
3.3.1 De'el%p Test T"aceabilit- D%c(#etati%
3.+ Set Up the Acceptace Testi, E'i"%#et
3.+.1 E'i"%#et P"epa"ati%
3.+.2 Ha"*$a"e2S%)t$a"e
3.. C%*(ct Acceptace Test Rea*iess Re'ie$ (ATRR)
3./ E3ec(te Tests
3./.1 Rec%"* Iss(es2De)ects
3./.2 Retesti, C%""ecte* S%)t$a"e
3./.3 Acceptace Re,"essi% Testi,
3./.+ D%c(#et Acceptace Test Res(lts
3.1 C%*(ct Acceptace Test Stat(s 0eeti,s
3.4 Acceptace Test Deli'e"ables
3.5 S(pp%"t Cliet Acceptace
1 ACCE-TANCE TEST ENTRANCE 5 E:#T CR#TER#A
+.1 Acceptace Test Et"ace C"ite"ia
+.2 Acceptace Test E3it C"ite"ia
2 RE-ORTS
..1 Ite"i# Stat(s Rep%"ti,
..2 Iss(e2De)ect Rep%"ti,
..3 Acceptace Test S(##a"- Rep%"t
..+ Acceptace Test !ial Rep%"t
3 R#S<S
A--END#CES
A--END#: A = ACRON%M )#ST