C System Test Plan_v1.0 Document

8/16/2019 C System Test Plan_v1.0 Document

1/24

System Test Plan

Responsible Author

Accountable Owner

Date 10/04/2014

Version + status 1.0 (Signe O!! Docu"ent#

$ro%ect &D $D211'

$age 1 o! 24

on!iential $D211')D$) *est $lan)1.0


2/24

REFERENCE TO CONTENTS

DP_ SYSTEM TEST PLAN............................................................................................1

1 INTRODUCTION......................................................................................................4

1.1 DOCUMENT BACKGROUND....................................................................................................4

1.2 REFERENCES.......................................................................................................................... 5

1.3 GENERAL................................................................................................................................5

1.4 DOCUMENT SCOPE................................................................................................................5

2 PROJECT CONTEXT.................................................................................................7

2.1 TEST ITEMS............................................................................................................................7

2.1 HARDWARE/ ENVIRONMENTS.............................................................................................7

3 FEATURES TO BE TESTED.......................................................................................8

3.1 INTERFACES............................................................................................................................... 9

4 FEATURES NOT TO BE TESTED..............................................................................10

5 TEST APPROACH..................................................................................................11

5.1 PLANNING APPROACH................................................................................................................ 11

5.2 TEST ACTIVITIES....................................................................................................................... 12

5.3 TESTING TECHNIUES............................................................................................................... 12

5.3.1 S TATIC TESTING.................................................................................................................... 12

5.3.2 SMOKE TESTING.................................................................................................................... 12

5.3.3 MANUAL TESTING.................................................................................................................. 12

5.3.4 REGRESSION TESTING............................................................................................................13

5.3.! E"PLORATOR# TESTING...........................................................................................................135.4 MULTIPLE BROWSER TESTING.....................................................................................................13

5.5 SITE ACCEPTANCE TESTING $FAT SUPPORT%...................................................................................14

5.! EARL# INTEGRATED S #STEM TESTING............................................................................................14

5.7 TEST DATA CONSIDERATIONS......................................................................................................14

5.& SUMMAR# REPORTING AND ANAL#SIS............................................................................................14

ENTRY AND EXIT CRITERION.................................................................................15

7 TEST SCHEDULE...................................................................................................17

8 TEST TOOLS.........................................................................................................1!

! ROLES " RESPONSIBILITIES..................................................................................20

10 RESOURCE " TRAININ# NEEDS............................................................................21

11 RIS$S% ASSUMPTIONS% ISSUES " DEPENDENCIES.................................................22

12 ASSUMPTIONS........................................................................................................................... 22

13 ISSUES.................................................................................................................................... 23

14 DEPENDENCIES......................................................................................................................... 23

15 DOCUMENT MANA#EMENT..................................................................................24

REFERENCE TO TABLES

*able 1, Docu"ent Re!erence.............................................................................................................................. -

$age 2 o! 24



3/24


4/24

1 INTRODUCTION

1.1 DO9:;* RO9;D

*his ocu"ent will allow all ?s sta@eholers incluing business technical an progra""e "anage"ent to

agree to the propose B S3ste" *esting actiities !or Delier3 $ass (D$# pro%ect an elierables prior to theco""ence"ent o! these actiities.

*he ocu"ent will proie etails o! ob%ecties !or B s3ste" testing phase within the eelop"ent an elier3o! this pro%ect.

*he below iagra" ta@en !ro" the s Organisational *est Strateg3 shows the relationship this ocu"ent (BS3ste" *est $hase *est $lan# has with the wier s test elierables.

igure 1, Docu"ent 6ierarch3

$age 4 o! 24

$D211')D$)S3ste" *est $lan)1.0


5/24

1.2 RR;S

Referene !ers"#n

$D0-)115)D)hec@out)2.5 (Strategic Delier3 $ass# 2.5

$D211')002)D)Strategic Delier3 $ass ontact entre 1.0 1.0

$D211')04)D) Strategic Delier3 $ass "ails 1.0 1.0

$D211')01)D) Delier3 $ass ront n 1.0 1.0

$D211')00')D)Strategic Delier3 $ass C &ntegration $oints 1.0 1.0

s :obile Annotate Cire!ra"e 0.10 (Strategic Delier3 $ass# .1

$D0-)120)D)Orer7i!ec3cle)2.5 (Strategic Delier3 $ass# 2.5

$D211')0-)D) Delier3 $ass Slot ;RA7

*he purpose o! this ocu"ent is to proie a etaile oeriew on the approach that will be aopte !or theS3ste" *esting o! D$ pro%ect !or B elierables. *his will be use as a pri"ar3 resource b3 all testpro!essionals in regars to what nees to be teste how to test the testing process an re!erences that will be

neee in orer to success!ull3 test the changes !or this pro%ect.*he signo!! o! this ocu"ent inicates that the signing reiewers approe the state test approach !or this testphase o! D$. &! changes to this plan are reEuire the3 will nee to be agree upon an signe o!! b3 thoseienti!ie as signatories in this ocu"ent.

*his test plan will be upate an reissue in the eent o! a signi!icant replan or "a%or scope changes to thepro%ect.

1.4 DO9:;* SO$

1$4$1 Inl%&e&

*his S3ste" *est $lan ocu"ent inclues,

• B S3ste" testing scope

• *he high leel entr3 an eit criteria !or B S3ste" *est phase.

• *he approach !or this S3ste" *est phase.

• *he resources elierables "etrics ti"elines issues ris@s eniron"ent an tools reEuire to

acco"plish test success !or this test phase.

1$4$2 E'l%&e&

*his S3ste" *est $lan ocu"ent eclues,

$age ( o! 24



6/24

• *he progra""e approach to *est Data S&* A* 9A* VF$ an an3 other subseEuent integration

testing phases.

• *esting reEuire !or eniron"ent reainess !or new asse"bl3 eniron"ent.

• Securit3 *esting/$; *esting.

• S3ste" changes not in scope !or B eelop"ent.

$age ) o! 24



7/24

2 PRO*ECT CONTE+T

Delier3 $ass is a subscription serice aailable to ?s online custo"ers where custo"ers are o!!ere theoption o! pa3ing an up!ront !ee !or a GDelier3 $ass? there!ore not incurring a charge on elier3 o! their onlineshop !or the subscription perio.

*he strategic solution o!!ers increase !unctionalit3 that will bene!it both colleagues an custo"ers. or

custo"ers the tactical solution will o!!er, a s"oother custo"er %ourne3 without the nee !or >O7 aresseri!ication auto"atic renewals ;ectar point accruals an better eperience on the >O7 site.

or colleagues the tactical solution o!!ers, colleague iscount i"proe !inancial an "anage"ent reportingintegration with the ontact entre s3ste" HS 7ogic an a plat!or" that will enable subseEuent si"ilarcusto"er o!!erings to be built.

*he purpose o! the pro%ect is to elier change b3,

a# Si"pli!3ing the process o! creation F "anage"ent o! elier3 passes !or business users.

b# Allowing custo"ers to bu3 elier3 passes ia etene saers site.

c# Allowing custo"ers to iew an "anage their elier3 pass !ro" eisting I:3 AccountJ section.

# $roiing a reliable plat!or" ia contact centre !or SR to help resole custo"er Eueries an issuesregaring elier3 pass.

e# :a@ing the process o! bu3ing elier3 pass "ore intuitie !or custo"ers with no elier3 pass.

!# &"ple"entation o! new pa3"ent proier to "a@e !irst ti"e an autorenew pa3"ents.

&t is worth noting that this pro%ect is epecte to be eliere a!ter the Proteus rollout is co"plete which "eansBlue Martini will not be !ul!illing an3 grocer3 orers at that ti"e.

2.1 *S* &*:S

*he s3ste"s to be consiere in scope o! B S3ste" testing !or D$ pro%ect are ienti!ie below,

S#,e Deta"ls

Applications (Cebsphereo""erce#

>O7 Des@top an :obile Sites

s Saers Site

:anage"ent entre

ontact entre

Reporting

&nter!aces;ew an hange &nter!aces. or etails please re!er to Section 1'.2o! this ocu"ent

*able 2, So!tware ite"s to be teste

2.1 6ARDCAR/ ;V&RO;:;*S

S3ste" testing will be one on one o! the eisting B S3ste" test eniron"ents in the initial stages o! testing.Chen an integrate s Asse"bl3 eniron"ent is aailable s3ste" testing actiities will be "oe to thisasse"bl3 eniron"ent i! it oes not cause an3 i"pact on testing.

:obile testing will be conucte using "obile hansets an web e"ulators uring initial s3ste" testing using B:obile networ@ in Cat!or. On s asse"bl3 eniron"ents web e"ulators will be use. See section -.4 !oretails o! "obile browsers that will be coere in s3ste" test.

$age - o! 24



8/24

3 FEATURES TO BE TESTED

DP F%nt"#nal ."/0 Leel Senar"#s

ount o! the scenarios is classi!ie base on business riers an !unctional classi!ication o! reEuire"ents.Re!er G6igh 7eel *est onitions 0.1.ls? !or etails.

F%nt"#nal Des"/n D# N# #f TestSenar"#s

Re%"rementsUse ases C#ere&

$D211')01)D) Delier3 $ass ront n 1.0 2- D$)9)001)Setup

D$)9)002)View D$

D$)9)00')


9/24

'.1 &nter!aces

*he !una"ental ai" o! &nter!ace *esting within S3ste" test will be to con!ir" the "oe"ent o! ata into anout o! eternal s3ste"s i.e. an3 s3ste" co""unicating with CebSphere o""erce is as speci!ie/esignean has not been aersel3 i"pacte b3 the changes "ae uner D$ pro%ect.

ollowing eisting inter!aces are i"pacte b3 the !unctional changes in D$ an there!ore are in scope o! BS3ste" testing K

&;*)0 on!ir"e Orers tract (CLC6# Outboun ile/tract

&;*)0- ODS etracts !or D$/Vouchers &nter!ace

&;*)15 $ublish olleague Discount

*7> Ceb serice

*he testing o! inter!aces inoling !ile trans!ers is straight !orwar an inoles the creation o! a !ile in the"atching !or"at (or ieall3 an ob!uscate real !ile that can be a"ene#. *he !ile content is "anipulate to"eet the test conitions reEuire an place in the appropriate irector3 on C !ro" which the triggeringprocess an subseEuent business processes can be chec@e.

&nter!aces that reEuire web serice interactions between C an a 'r part3 s3ste" will be teste through!unctional test scripts. *he inter!aces reEuiring integration between C an


10/24

4 FEATURES NOT TO BE TESTED

ollowing ite"s are out o! scope !or this test phase,

• S3ste" testing o! an3 co"ponents not in scope !or B eelop"ent.

• S3ste" &ntegration testing between Cebsphere co""erce an other thir part3 applications incluing

D2D reporting solution C6 nectar etc.

• hanges in the unctional Designs not releant to D$ pro%ect. *he testing o! these changes resulting !ro"

$roteus e!ects / changes will not be coere in this test plan.

• *he test elierables eecution an "anage"ent o! Volu"e an $er!or"ance *esting as this will be the

sub%ect o! its own $hase *est $lan.

• An3 changes which will be eplo3e as the result o! the $roteus :aintenance Releases an "erger to the

D$ coe is out o! scope !or this test plan an hae to be coere separatel3.

• *est elierables eecution an "anage"ent o! Securit3 or $; testing as this will be the sub%ect o! its

own $hase *est $lan.

• An3 changes to Reports which "a@e use o! ata !ro" ODS.

• Accessibilit3 testing Operational reainess :igration o! tactical elier3 passes into strategic solution.

$age 17 o! 24



11/24

( TEST APPROAC.

-.1 $lanning Approach

D$ S3ste" testing is planne to be one in three rops with each rops aing on to preiousl3 eliere

!unctionalit3. D$ S3ste" *esting will !ollow a preplanne incre"ental elier3 (phase# approach. Cith eachincre"ent new !unctionalit3 will be ae !or s3ste" testing. *his approach gies the testing tea" earl3 sighto! the coe an !acilitates earl3 testing an !eebac@ on Eualit3 to the eelop"ent tea". &t enables !or"alphases o! ?s testing to co""ence earl3 in the buil phase an reuces oerall buil phase uration.

*he approach reEuires the elier3 !ro" eelop"ent o! a nu"ber o! Grops? each co"prising a @nown set o!co"plete !unctionalit3.

S3ste" *esting will progress through ' pri"ar3 coe rops that co"prise o! the !ollowing high leel !unctionalcategorisations

• Drop 1 (on!iguration#,

o Setting up tene Site on :

o R:S uploa o! D$ S=9s incluing status upates

o Setting up D$ catalogue !or etene sites

o reation o! D$ on tene Site

o Displa3 D$ on Saers site ho"epage

o 6eaer an ooter

• Drop 2 (usto"er Hourne3s#,

o Delier3 slot oerla3 page on >O7 site with ouchers

o Saers site integration with >O7 site

o Delier3 $ass an Delier3 $ricing Ruleso hec@out %ourne3s !or D$ purchase !ro" Saers site

o "ails !or tene site !or orer con!ir"ation

o :3 $asses

o Delier3 slots ispla3 !or D$ aailable to custo"er

o $lacing >O7 orers with D$

o :obile site changes !or D$

o Single sign on an Registration on s Saer site

o

ontent :anage"ento hanges to &;*- (ODS#

• Drop ' (ontact entre#,

o ontact entre changes !or D$ (


12/24

-.2 *est Actiities

S3ste" *esting $hase will co"prise o! !ollowing actiities,

• reation o! 6igh 7eel *est Scenarios/ onitions ("bee in this ocu"ent#

• reation o! etaile *est Scripts an baseline uploa to Mualit3 entre

• S"o@e testing o! each coe rop

• ecution o! scheule test cases i.e. testing the !unctionalit3 co"prising each coe rop

• De!ect Reporting an Dail3 *riage with B Deelop"ent tea"

• Retest e!ect !ies applie in each coe rop

• reation o! regular S3ste" *est ecution Reports

• &ssue an Signo!! !or S3ste" *est $hase losure Report

All coe releases will be planne in aance an ocu"ente in the etaile S3ste" *est scheule. *his willbe integrate into the B $ro%ect/


13/24

*he newl3 create/ upate tests will be eecute "anuall3 b3 pro!essional test anal3sts. A nu"ber o!stanar testing techniEues will be !ollowe,


14/24

or the ontact entre user o! HS 7ogic,

• &10

• &5/ &

-.- Site Acceptance *esting (A* Support#

B *est *ea" will support preA* testing b3 holing wal@through sessions with s *est *ea" ahea o! eachcoe rop elier3 to a s integration eniron"ent. Detaile plan !or these sessions will be agree uringS3ste" test eecution between B *est :anager an s *est :anager.

-. arl3 &ntegrate S3ste" *esting

&n orer to reuce the ris@ o! test case !ailures uring A* an S&* an earl3 integrate/asse"bl3 test will beplanne uring s3ste" test phase to test B elierables with Gtouching? applications prouce b3 othersuppliers. *his testing is sub%ect to aailabilit3 o! this asse"bl3 eniron"ent !ro" s an will be conucte i!not ee"e to cause ela3s in test co"pletion.

At the ti"e o! writing this ocu"ent the proposal ha not been !inalise an is uner elaboration. *hescheuling o! coe releases will nee to be ti"e to coincie with the co"pletion o! S3ste" *esting c3cles !ro"arious suppliers an necessar3 support "ae aailable.

-. *est Data onsierations

&nitial test ata is ienti!ie base on the 6igh leel *est onitions. B *est Anal3sts will collate a spreasheetthat etails the @e3 ata conitions reEuire an will @eep aing the ata along with *est script preparationan eecution.

-. Su""ar3 Reporting an Anal3sis

*he reporting o! S3ste" *esting progress will be the responsibilit3 o! the B *est "anager or elegate B *estlea. &n aition the *est :anager/7ea will report progress internall3 to the B $rogra""e :anager an theDeelop"ent $ro%ect :anager. *his will be supple"ente b3 perioic reiew b3 the B *esting unctional 7ea.*he !ollowing elierables will be the responsibilit3 o! the B *est :anager,

• $repare a *est erti!icate at the start o! testing an co"pletion o! S3ste" *esting (an internal B Mualit3

>ate#.

• $repare a etaile e!ect report (will !or" part o! the test co"pletion report#.

• $roie in!or"ation to support B pro%ect "anage"ent wee@l3 status su""ar3 "eetings.

• $repare an issue a test phase closure report at the en o! the S3ste" *esting phase. *he S3ste" *est

:anager will be responsible !or ti"el3 reiew an progra""e signo!! o! the S3ste" *est losure report.

$age 14 o! 24



15/24

) ENTR8 AND E+IT CRITERION

*his section outlines the Eualit3 gate criteria that "ust be reiewe when entering or eiting the S3ste" *estphase.


16/24

Euall3 the nu"bers aboe "a3 be eceee but the i"pact to ownstrea" testing phases is iewe asli"ite an as such transition out o! S3ste" *esting "a3 still be achiee.

Seer"ty leel Def"n"t"#n

1 ritical A De!ect reners all or a "a%orit3 o! the s3ste" uner test inoperable. *his "a3

inclue a "a%or area o! the s3ste" being a!!ecte b3 the incient an it is signi!icant toassociate business processes.

a"ples "ight inclue, a s3ste" crash or unaailabilit3 signi!icant ata corruption orata loss securit3 ulnerabilit3 or loss o! an entire !unctional area resulting in the"a%orit3 o! test scripts !or that area being bloc@e.

2 :a%or An ele"ent o! a high priorit3 !eature or !unction oes not wor@ an is preenting a"inorit3 o! test scripts being co"plete. A wor@aroun "a3 be aailable !or testpurposes but it is not acceptable to business users.

3 Aerage A De!ect is ienti!ie that oes not preent the co"pletion o! an entoen test butoes cause the !ailure o! a speci!ic test step within that entoen test process an inrespect o! the De!ect there is a wor@aroun agree with the lient which allows that

area o! !unctionalit3 to be use within the releant business processes.

4 :inor *his is !or "inor proble"s such as !ailures at etre"e bounar3 conitions that areunli@el3 to occur in nor"al use or "inor errors in la3out/!or"atting. $roble"s o! thist3pe o not i"pact use o! the prouct in an3 substantie wa3. *hese are incients thatare cos"etic in nature an o! no or er3 low i"pact to business processes.

*able , De!ect Seerit3 e!initions

*hese e!ect seerit3 leels will be use throughout B S3ste" *est phase an !or e!ect !i support in thesubseEuent ?s test phases

$age 1) o! 24



17/24

- TEST SC.EDULE

System Test Tas9s Start Date En& Date

Test Plann"n/ : Test Senar"# Pre,arat"#n

*est $lan reation an &ssue !or reiew 24 :ar 2014 10 Apr 2014

*est $lan Reiew an SignO!! 10 Apr 2014 1 Apr 2014Test Sr",t Pre,arat"#n

Detaile *est Scripts $reparation (Drop 1# 24 :ar 2014 4 Apr 2014

Detaile *est Scripts $reparation (Drop 2+'# Apr 2014 '0 Apr 2014

System Test E'e%t"#n

Drop1 (:anage"ent entre + Saer Site6o"epage# Apr 2014 2 Apr 2014

Drop2 + Drop' (Saer Site + ontact entre +Delier3 Slot + ODS# 1 :a3 2014 1 Hun 2014

System Test Re/ress"#n

*argete regression o! i"pacte !unctions 15 Hun 2014 2 Hul 2014

System Test P0ase Cl#s%re*est $hase losure Report (&ssue# ' Hul 2014 5 Hul 2014

*able , S3ste" *esting 6igh 7eel Scheule8

igure 2, *est Scheule

C1...C1'P Cee@1Cee@1'n


18/24

will be "ae irectl3 to the B


19/24

5 TEST TOOLS

.P


20/24

6 ROLES : RESPONSIBILITIES

T"tle Res,#ns"?"l"ty

B $ro%ect :anager

• hange :anage"ent $rocess

• nsure all ocu"ents are baseline an signe o!! be!ore

eelop"ent/testing start

B *est :anager

• reation o! S3ste" *est $lan (*his Docu"ent#

• oorinate *est Actiities

• Reiew *est Scenarios

• arr3out De!ect *riage :eeting

• 6ighlight Ris@s uring *esting

• $rouce *est o"pletion Report

*est Anal3sts

• reate *est Scenarios an Scripts !or assigne !unctional areas

• ecute *est scripts

• 7og e!ects

•De!ect retest

• 6ighlight an3 Ris@ associate to their assigne tas@s

B De *ea"

• Docu"ent the !unctional epenencies

• Application eelop"ent an unit testing

• :anage /


21/24

17 RESOURCE : TRAINING NEEDS

;o !urther *raining has been ienti!ie as neee !or the B *est tea" that nees to be incorporate into theS3ste" *esting ti"elines.

$age 21 o! 24



22/24

11 RIS@S ASSU>PTIONS ISSUES : DEPENDENCIES

R"s9 Desr",t"#n Im,at(1&nsigni!icant 2:inor ':oerate4:a%or -Seere#

L"9el"0##&(1Re"ote 29nli@el3'$ossible 4$robable

-Al"ost ertain#

Seer"ty(&"pact

7i@elihoo#

>"t"/at"n/ At"#n At"#n Oner

Real test ata aailabilit3uring the S3ste" testingphase

4 ' 12 B *est :anager will engage with the business usersto proie sa"ple ata set !or setting up real li@eD$s.

B *est :anager

&ntegrate S3ste" *est Asse"bl3 eniron"ent is not

aailable !or co""ence"ento! B S3ste" testing

' ' 5 B S3ste" *est eniron"ent will be use to startS3ste" *esting actiities.

B *est :anager

*7> integration not proen!or *est eniron"ents be!orestart o! Drop2.

4 ' 12 *esting will continue with *7> web serice isablean i"pacte scenarios will be reisite once *7>web serices are setup.

B De :anager

Asse"bl3 eniron"ent iseliere to S* tea" withouteniron"ent proing.

4 ' 12 *est tea" will carr3 out eniron"ent proing on newasse"bl3 eniron"ent which will i"pact testscheule b3 1.- 2 wee@s.

B *est :anager

12 Assu"ptions

Ass%m,t"#n Desr",t"#n Im,at If False At"#n Oner

S3ste" *est n is aailable with *7> !or co""ence"ent o! S*.

$age 22 o! 24



23/24

1' &ssues

;/A

14 Depenencies

De,en&eny De,en&eny Oner

Support !ro" *7> tea" uring s3ste" testing with anacceptable response ti"e.

Support !ro" R:S tea" to help setup D$ proucts.

$age 23 o! 24



24/24

1( D#%ment >ana/ement

D#%ment I&ent"f"er

$D211')D$)B S3ste" *est $lan)1.0

D#%ment L#at"#n

Re"s"#n ."st#ry

Sta/e !ers"#n Date A%t0#r s Re"eer S%mmary #f C0an/es

Dra!t 0.1 10/04/2014 =a"al

Date post:	05-Jul-2018
Category:	Documents
Upload:	akin
View:	215 times
Download:	0 times

C System Test Plan_v1.0 Document

Documents