automation test plan template1

8/10/2019 Automation Test Plan Template1

1/28

Generic Project

Prepared for

Project Name

Prepared by

Company Name

Date

July 17, 2001

2001, COMPANY NAME All ri!"t# re#er$e%

&"i# %ocumentation i# t"e con'i%ential an% proprietary intellectual

property o' COMPANY NAME Any unaut"ori(e% u#e,

repro%uction, preparation o' %eri$ati$e )or*#, per'ormance, or

%i#play o' t"i# %ocument, or #o't)are repre#ente% +y t"i#

%ocument, )it"out t"e epre## )ritten permi##ion o' COMPANY i#

#trictly pro"i+ite%

COMPANY NAME an% t"e COMPANY NAME lo!o %e#i!n are

tra%emar*# an%-or #er$ice mar*# o' an a''iliate o' COMPANY

NAME All ot"er tra%emar*#, #er$ice mar*#, an% tra%e name# are

o)ne% +y t"eir re#pecti$e companie#


2/28


3/28

PROJECT NAMETemplate

D O C U M E N T R E V I S I O N I N F O R M A T I O N

&"e 'ollo)in! in'ormation i# to +e inclu%e% )it" all $er#ion# o' t"e %ocument

Project Name Project Number

Prepared by Date Prepared

Revised by Date Revised

Revision Reason Revision Control No.





Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% iii


4/28

PROJECT NAMETemplate

D O C U M E N T A P P R O V A L

&"i# #i!nature pa!e i# to in%icate appro$al 'rom COMPANY NAME#pon#or an% Client #pon#or 'or t"e attac"e% &emplate 'or

t"e P.OJEC& NAME All partie# "a$e re$ie)e% t"e attac"e% %ocument an% a!ree )it" it# content#

COMPAN NAM! Project Mana"er#

Name$ %itle# Project Mana"er$ PRO&!C% NAM!

Date

C'S%OM!R Project Mana"er#

Name$ %itle#

Date

COMPAN NAM!(D!PAR%M!N% Sponsor#

Name$ %itle#

Date

COMPAN NAM! Sponsor#

Name$ %itle#

Date

C'S%OM!R NAM! Sponsor#

Name$ %itle#

Date

COMPAN NAM! Mana"er#

Name$ %itle#

Date

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% i$


5/28

%able of Contents

) I n t r o d u c t i o n ...........................................................................................................)

11 Automate% &e#tin! /&P O$er$ie)1

* % e s t D e s c r i p t i o n ..................................................................................................*

21 &e#t %enti'ication 2

22 &e#t Purpo#e an% O+jecti$e#2

2 A##umption#, Con#traint#, an% Eclu#ion#2

2 Entry Criteria 2

23 Eit Criteria

24 Pa##-5ail Criteria

+ % e s t S c o p e ..............................................................................................................,

1 tem# to +e te#te% +y Automation3

2 tem# not to +e te#te% +y Automation3

- % e s t A p p r o a c ......................................................................................................./

1 /e#cription o' Approac"4

, % e s t D e f i n i t i o n .....................................................................................................0

31 &e#t 5unctionality /e'inition 6.euirement# &e#tin!87

32 &e#t Ca#e /e'inition 6&e#t /e#i!n87

3 &e#t /ata .euirement#7

3 Automation .ecor%in! 9tan%ar%#7

33 :oa%runner Menu 9ettin!#;

34 :oa%runner 9cript Namin! Con$ention#;

37 :oa%runner G


6/28

0 % e s t I s s u e s a n d R i s 1 s ...................................................................................) -

71 ##ue#1

72 .i#*#1

2 A p p e n d i c e s ...........................................................................................................)/

;1 &racea+ility Matri 14

;2 /e'inition# 'or Eample Cre%it car% num+er#2

).) A u to m a te d % e s t i n " D % P O v e r v i e 5

This Automated Testing Detail Test Plan (ADTP) will identify the speifi tests that a!e to "e

pe!fo!med to ensu!e the #uality of the deli$e!ed p!odut% &ystem'nteg!ation Test ensu!es the p!odut

funtions as designed and all pa!ts wo! togethe!% This ADTP will o$e! info!mation fo! Automatedtesting du!ing the &ystem'nteg!ation Phase of the p!o*et and will map to the speifiation o!

!e#ui!ements doumentation fo! the p!o*et% This mapping is done in on*untion with the

T!aea"ility Mat!i+ doument, that should "e ompleted along with the ADTP and is !efe!ened in

this doument%

This ADTP !efe!s to the speifi po!tion of the p!odut nown as PROD-CT NAME% t p!o$ides

lea! ent!y and e+it !ite!ia, and !oles and !esponsi"ilities of the Automated Test Team a!e identified

suh that they an e+eute the test%

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% &a+le o' Content# $i

Introduction


7/28

The o"*eti$es of this ADTP a!e/

0 Des!i"e the test to "e e+euted%

0 dentify and assign a uni#ue num"e! fo! eah speifi test%

0 Des!i"e the sope of the testing%

0 1ist what is and is not to "e tested%

0 Des!i"e the test app!oah detailing methods, tehni#ues, and tools%

0 Outline the Test Design inluding/

2untionality to "e tested%

Test Case Definition%

Test Data Re#ui!ements%

0 dentify all speifiations fo! p!epa!ation%

0 dentify issues and !iss%

0 dentify atual test ases%

0 Doument the design point o! !e#ui!ement tested fo! eah test ase as it is de$eloped%

).* %est Ide n t i f i ca t i on

This ADTP is intended to p!o$ide info!mation fo! &ystem'nteg!ation Testing fo! the PROD-CT

NAME module of the PROJECT NAME% The test effo!t may "e !efe!!ed to "y its PROJECT

RE3-E&T (PR) num"e! and its p!o*et title fo! t!aing and monito!ing of the testing p!og!ess%

).+ % e s t P u r p o s e a n d O b j e c t i v e s

Automated testing du!ing the &ystem'nteg!ation Phase as !efe!ened in this doument is intended to

ensu!e that the p!odut funtions as designed di!etly f!om ustome! !e#ui!ements% The testing goal

is to identify the #uality of the st!utu!e, ontent, au!ay and onsisteny, some !esponse times and

lateny, and pe!fo!mane of the appliation as defined in the p!o*et doumentation%

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% &a+le o' Content# $ii

%est Description


8/28

).- A s s u m p t i o n s $ C o n s t ra i n ts $ a n d ! 6 c l u s i o n s

2ato!s whih may affet the automated testing effo!t, and may in!ease the !is assoiated with the

suess of the test inlude/

0 Completion of de$elopment of f!ont5end p!oesses0 Completion of design and onst!ution of new p!oesses

0 Completion of modifiations to the loal data"ase

0 Mo$ement o! implementation of the solution to the app!op!iate testing o! p!odution en$i!onment

0 &ta"ility of the testing o! p!odution en$i!onment

0 1oad Disipline

0 Maintaining !eo!ding standa!ds and automated p!oesses fo! the p!o*et

0 Completion of manual testing th!ough all applia"le paths to ensu!e that !eusa"le automated

s!ipts a!e $alid

)., !n t ry C r i te r i a

The ADTP is omplete, e+luding atual test !esults% The ADTP has "een signed5off "y app!op!iate

sponso! !ep!esentati$es indiating onsent of the plan fo! testing%

The P!o"lem T!aing and Repo!ting tool is !eady fo! use% The Change Management and

Configu!ation Management !ules a!e in plae%

The en$i!onment fo! testing, inluding data"ases, appliation p!og!ams, and onneti$ity has "een

defined, onst!uted, and $e!ified%

)./ !6 i t Cr i t e r ia

n esta"lishing the e+it'aeptane !ite!ia fo! the Automated Testing du!ing the &ystem'nteg!ation

Phase of the test, the P!o*et Completion C!ite!ia defined in the P!o*et Definition Doument (PDD)

should p!o$ide a sta!ting point% All automated test ases ha$e "een e+euted as doumented% The

pe!ent of suessfully e+euted test ases met the defined !ite!ia% Reommended !ite!ia/ No

C!itial o! 6igh se$e!ity p!o"lem logs !emain open and all Medium p!o"lem logs ha$e ag!eed upon

ation plans7 suessful e+eution of the appliation to $alidate au!ay of data, inte!faes, and

onneti$ity%

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% &a+le o' Content# $iii


9/28

).0 Pass (7a i l C r i te r ia

The !esults fo! eah test must "e ompa!ed to the p!e5defined e+peted test !esults, as doumented in

the ADTP (and DTP whe!e applia"le)% The atual !esults a!e logged in the Test Case detail within

the Detail Test Plan if those !esults diffe! f!om the e+peted !esults% f the atual !esults math the

e+peted !esults, the Test Case an "e ma!ed as a passed item, without logging the dupliated !esults%

A test ase passes if it p!odues the e+peted !esults as doumented in the ADTP o! Detail Test Plan

(manual test plan)% A test ase fails if the atual !esults p!odued "y its e+eution do not math the

e+peted !esults% The sou!e of failu!e may "e the appliation unde! test, the test ase, the e+peted

!esults, o! the data in the test en$i!onment% Test ase failu!es must "e logged !ega!dless of the sou!e

of the failu!e%

Any "ugs o! p!o"lems will "e logged in the DE2ECT TRAC8N9 TOO1%

The !esponsi"le appliation !esou!e o!!ets the p!o"lem and tests the !epai!% One this is omplete,

the teste! who gene!ated the p!o"lem log is notified, and the item is !e5tested% f the !etest is

suessful, the status is updated and the p!o"lem log is losed%

f the !etest is unsuessful, o! if anothe! p!o"lem has "een identified, the p!o"lem log status is

updated and the p!o"lem des!iption is updated with the new findings% t is then !etu!ned to the

!esponsi"le appliation pe!sonnel fo! o!!etion and test%

&e$e!ity Codes a!e used to p!io!iti:e wo! in the test phase% They a!e assigned "y the test g!oup and

a!e not modifia"le "y any othe! g!oup% The following standa!d &e$e!ity Codes to "e used fo!

identifying defets a!e/

&a+le 1Severity Codes

Severity Code

Number

Severity Code

Name Description

1 Critical Automate% te#t# cannot procee% 'urt"er )it"in applica+le te#tca#e 6no )or* aroun%8

2 ?i!" &"e te#t ca#e or proce%ure can +e complete%, +ut pro%uce#incorrect output )"en $ali% in'ormation i# input

Me%ium &"e te#t ca#e or proce%ure can +e complete% an% pro%uce#correct output )"en $ali% in'ormation i# input, +ut pro%uce#incorrect output )"en in$ali% in'ormation i# input

6e! no #pecial c"aracter# are allo)e% a# part o' #peci'ication#

+ut )"en a #pecial c"aracter i# a part o' t"e te#t an% t"e#y#tem allo)# a u#er to continue, t"i# i# a me%ium #e$erity8

:o) All te#t ca#e# an% proce%ure# pa##e% a# )ritten, +ut t"erecoul% +e minor re$i#ion#, co#metic c"an!e#, etc &"e#e%e'ect# %o not impact 'unctional eecution o' #y#tem

The use of the standa!d &e$e!ity Codes p!odues fou! ma*o! "enefits/

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% &a+le o' Content# i


10/28

0 &tanda!d &e$e!ity Codes a!e o"*eti$e and an "e easily and au!ately assigned "y those

e+euting the test% Time spent in disussion a"out the app!op!iate p!io!ity of a p!o"lem is

minimi:ed%

0 &tanda!d &e$e!ity Code definitions allow an independent assessment of the !is to the on5shedule

deli$e!y of a p!odut that funtions as doumented in the !e#ui!ements and design douments%

0 -se of the standa!d &e$e!ity Codes wo!s to ensu!e onsisteny in the !e#ui!ements, design, and

test doumentation with an app!op!iate le$el of detail th!oughout%

0 -se of the standa!d &e$e!ity Codes p!omote effeti$e esalation p!oedu!es%

The sope of testing identifies the items whih will "e tested and the items whih will not "e tested

within the &ystem'nteg!ation Phase of testing%

).2 I t e m s to b e te s t e d b y A u to m a t i o n

.% PROD-CT NAME

4% PROD-CT NAME

;% PROD-CT NAME


11/28

).)8 Des cr i p t i on o f Ap pr oac

The mission of Automated Testing is the p!oess of identifying !eo!da"le test ases th!ough all

app!op!iate paths of a we"site, !eating !epeata"le s!ipts, inte!p!eting test !esults, and !epo!ting to

p!o*et management% 2o! the 9ene!i P!o*et, the automation test team will fous on positi$e testing

and will omplement the manual testing unde!gone on the system% Automated test !esults will "e

gene!ated, fo!matted into !epo!ts and p!o$ided on a onsistent "asis to 9ene!i p!o*et management%

&ystem testing is the p!oess of testing an integ!ated ha!dwa!e and softwa!e system to $e!ify that the

system meets its speified !e#ui!ements% t $e!ifies p!ope! e+eution of the enti!e set of appliation

omponents inluding inte!faes to othe! appliations% P!o*et teams of de$elope!s and test analysts

a!e !esponsi"le fo! ensu!ing that this le$el of testing is pe!fo!med%

nteg!ation testing is onduted to dete!mine whethe! o! not all omponents of the system a!e

wo!ing togethe! p!ope!ly% This testing fouses on how well all pa!ts of the we" site hold togethe!,

whethe! inside and outside the we"site a!e wo!ing, and whethe! all pa!ts of the we"site a!e

onneted% P!o*et teams of de$elope!s and test analyst a!e !esponsi"le fo! ensu!ing that this le$el of

testing is pe!fo!med%

2o! this p!o*et, the &ystem and nteg!ation ADTP and Detail Test Plan omplement eah othe!%

&ine the goal of the &ystem and nteg!ation phase testing is to identify the #uality of the st!utu!e,

ontent, au!ay and onsisteny, !esponse time and lateny, and pe!fo!mane of the appliation, test

ases a!e inluded whih fous on dete!mining how well this #uality goal is aomplished%

Content testing fouses on whethe! the ontent of the pages math what is supposed to "e the!e,

whethe! ey ph!ases e+ist ontinually in hangea"le pages, and whethe! the pages maintain #uality

ontent f!om $e!sion to $e!sion%

Au!ay and onsisteny testing fouses on whethe! today>s opies of the pages download the same

as yeste!day>s, and whethe! the data p!esented to the use! is au!ate enough%

Response time and lateny testing fouses on whethe! the we" site se!$e! !esponds to a "!owse!

!e#uest within e!tain pe!fo!mane pa!amete!s, whethe! !esponse time afte! a &-?MT is aepta"le,

o! whethe! pa!ts of a site a!e so slow that the use! disontinues wo!ing% Although 1oad!unne!

p!o$ides the full measu!e of this test, the!e will "e $a!ious AD 6OC time measu!ements within

e!tain 1oad!unne! &!ipts as needed%


%est Approac


12/28

Pe!fo!mane testing (1oad!unne!) fouses on whethe! pe!fo!mane $a!ies "y time of day o! "y load

and usage, and whethe! pe!fo!mane is ade#uate fo! the appliation%

Completion of automated test ases is denoted in the test ases with indiation of pass'fail and follow5

up ation%

This setion add!esses the de$elopment of the omponents !e#ui!ed fo! the speifi test% nluded a!e

identifiation of the funtionality to "e tested "y automation, the assoiated automated test ases and

sena!ios% The de$elopment of the test omponents pa!allels, with a slight lag, the de$elopment of

the assoiated p!odut omponents%

).)) % e s t 7 u n c t i o n a l i t y D e f i n i t i o n 9 R e : u i re m e n ts

% e s t i n " ;

The funtionality to "e automated tested is listed in the T!aea"ility Mat!i+, attahed as an appendi+%

2o! eah funtion to unde!go testing "y automation, the Test Case is identified% Automated Test

Cases a!e gi$en uni#ue identifie!s to ena"le !oss5!efe!ening "etween !elated test doumentation,and to failitate t!aing and monito!ing the test p!og!ess%

As muh info!mation as is a$aila"le is ente!ed into the T!aea"ility Mat!i+ in o!de! to omplete the

sope of automation du!ing the &ystem'nteg!ation Phase of the test%

).)* %est Cas e De f in i t i on 9%est Des i"n ;

Eah Automated Test Case is designed to $alidate the assoiated funtionality of a stated !e#ui!ement%

Automated Test Cases inlude unam"iguous input and output speifiations% This info!mation is

doumented within the Automated Test Cases in Appendi+ @%= of this do%

).)+ %est Dat a Re: u i re me nt s

The automated test data !e#ui!ed fo! the test is des!i"ed "elow% The test data will "e used to

populate the data "ases and'o! files used "y the appliation'system du!ing the &ystem'nteg!ation

Phase of the test%

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% &a+le o' Content# ii

%est Definition


13/28

).)- Aut oma t i on Recor d i n" S ta nda rd s

nitial Automation Testing Rules fo! the 9ene!i P!o*et/

.% A"ility to mo$e th!ough all paths within the applia"le system

4% A"ility to identify and !eo!d the 9- Maps fo! all assoiated test items in eah path

;% &peifi times fo! loading into automation test en$i!onment


14/28


15/28

.% 1A? .., loated within the 9E Test 1a", will Ihouse the o!iginal 1oad!unne! &!ipt, Results and

Repo!t Reposito!y fo! automated testing within the 9ene!i P!o*et% RTE aess is g!anted

1oad!unne! Tehniians and READ ON1K aess is g!anted those who a!e autho!i:ed to !un

s!ipts "ut not mae any imp!o$ements% This is meant to maintain the pu!ity of eah s!ipt

$e!sion%

4% 1oad!unne! on 1A? D!i$e houses all 1oad!unne! !elated douments, et fo! 9E automated

testing%

;% P!o*et file folde!s fo! the 9ene!i P!o*et !ep!esent the initial st!utu!e of p!o*et folde!s

utili:ing automated testing% As ou! automation "eomes mo!e ad$aned, the st!utu!e will sp!ead

to othe! app!op!iate a!eas%


16/28

).*) %est !nv i r on me nt

&a+le 2!nvironmentfo! Automated Test

Automated Test en$i!onment is indiated "elow% E+isting dependenies a!e ente!ed in omments%

!nvironment %est System Comments

&e#t >

9y#tem-nte!ration &e#t

69&8

Cert Acce## $ia "ttp@---

Pro%uction Pro%uction Acce## $ia "ttp@-- )))

Ot"er 6#peci'y8 /e$elopment n%i$i%ual &e#t En$ironment#

&a+le =ard5arefo! Automated Test

The following is a list of the ha!dwa!e needed to !eate p!odution lie en$i!onment/

Manufacturer Device %ype

ariou# Per#onal Computer 6;4 or ?i!"er8 )it" monitor B reuire% perip"eral# )it"connecti$ity to internet te#t-pro%uction en$ironment# Mu#t +e ena+le% to

A//&ONA: .EDersion 9if applicable; Pro"rammer Support

5ire'o or "i!"er

nternet Eplorer or "i!"er

Sabre Inc.Con'i%ential-All .i!"t# .e#er$e% &a+le o' Content# $i

%est Preparation Specifications


17/28

).** %est %eam Ro le s and Resp ons ib i l i t i es

&a+le 3%est %eam Roles and Responsibilities

Role Responsibilities Name

COMPANY NAME9pon#or

Appro$e project %e$elopment, "an%le major i##ue# relate%to project %e$elopment, an% appro$e %e$elopmentre#ource#

Name, P"one

A+acu# 9pon#or 9i!nature appro$al o' t"e project, "an%le major i##ue# Name, P"one

A+acu# ProjectMana!er

En#ure# all a#pect# o' t"e project are +ein! a%%re##e%'rom C


18/28

) . * + % e s t % ea m % r a i n i n " R e : u i r e m e n t s

&a+le 4Automation %rainin" Re:uirements

%rainin"

Re:uirement %rainin" Approac

%ar"et Date for

Completion

Roles(Resources to

be %rained

) . * - A u t o m a t i o n % e s t P r e p a r a t i o n

.% !ite and !eei$e app!o$al of the ADTP f!om 9ene!i P!o*et management

4% Manually test the ases in the plan to mae su!e they atually wo! "efo!e !eo!ding !epeata"le

s!ipts

;% Reo!d app!op!iate s!ipts and file them ao!ding to the naming on$entions des!i"ed within

this doument


19/28

) . * , I s s u e s

The ta"le "elow lists nown p!o*et testing issues to date% -pon sign5off of the Detail Test Plan, this

ta"le will not "e maintained, and these issues and all new issues will "e t!aed th!ough the ssue

Management &ystem, as indiated in the p!o*ets app!o$ed ssue Management P!oess%

&a+le 7Issues

Issue Impact

%ar"et Date

for Resolution O5ner

COMPANY NAME te#t teami# not in po##e##ion o'mar*et %ata re!ar%in! )"at+ro)#er# are mo#t in u#e inC


20/28

2 Duality o'


21/28

hange and new !e#ui!ements an "e added% 6owe$e!, if new !e#ui!ements a!e added o! e+isting

!e#ui!ements a!e modified afte! the ?usiness Re#ui!ements doument and this doument ha$e "een

app!o$ed, the hanges will "e su"*et to the hange management p!oess%

The T!aea"ility Mat!i+ fo! this p!o*et will "e de$eloped and maintained "y the test oo!dinato!% At

the ompletion of the mat!i+ definition and the p!o*et, a opy will "e added to the p!o*et note"oo%



22/28

'unctional Areas of Tracea"ility atri I 5unctional Area Priority

1 Pon% E

2 .i$er E

:a*e

automation test plan template1

Documents