Testing Details

8/11/2019 Testing Details

1/45

ORANGE IT SOLUTIONS

Testing Manual

Page 1


2/45

ORANGE IT SOLUTIONS

CONTENTS

I. The Software life cycle

1.1 Feasibility Study1.2 Systems Analysis1.3 Systems Design1.4 Coding1.5 Testing1.6 Installation & Maintenane

2. Software Development ife Cycles

2.1. Code!and!"# model2.2. $ate%all model

2.3. '%ototy(ing model2.4 In%emental2.5 S(i%al model

!. Testing ife Cycle

3.1 System Study

3.2 So(e) A((%oa*) +stimation3.3 Test 'lan Design3.4 Test Cases Design

3.5 Test Case ,e-ie3.6Test Case +#eution

3./ Deet 0andling3. a( Analysis3.Deli-e%ables

" Testing #hases $ The % Mo&el

4.1 nit Testing4.2 Integ%ation Testing4.3 System Testing4.4 Ae(tane Testing

' Testing Metho&s $ ()**#SC Mo&el5.1 Funtionality Testing5.2 sability Testing

5.3 ,eliability Testing5.4 ,eg%ession Testing5.5 'e%o%mane Testing5.6 Salability Testing5./ Com(atibility Testing

+ #erformance ife Cycle

Page 2


3/45

(easi,ility Stu&y

Design

Co&ing

-nalysis

Testing

Installation Maintenance

ORANGE IT SOLUTIONS

6.1 What is Performance Testing6.2 Why Performance Testing6.3 Performance Testing

6.4 Load Testing

6.5 Stress Testing

6.6 When should we start Performance Testing

6./ 'o(ula% tools used to ondut 'e%o%mane Testing6. 'e%o%mane Test '%oess

/ ife Cycle of -utomation/.1 $*at is Automation/.2 ene"ts o Test Automation/.3 False ene"ts/.4 $*at a%e t*e di7e%ent tools a-ailable in t*e ma%8et

0 Testing imitations.1 Test Sto( C%ite%ia

1 Tester *esponsi,ilities

.1 0o to '%io%iti9e Tests

3 4ow can we improve the e5ciency in testing6

. The Software life cycle

All o t*e stages %om sta%t to "nis* t*at ta8e (lae *en de-elo(ing aneSota%e.

T*e sota%e lie!yle is a des%i(tion o t*e e-ents t*at ou%beteen t*e bi%t* and deat* o a sota%e (%o:et inlusi-ely.

Page 3

; (easi,ility Stu&y an& pro,lem -nalysis< $*at e#atly is t*is system su((osed to do

Dete%mine and s(ell out t*e details o t*e (%oblem.

; Design< 0o ill t*e system sol-e t*e (%oblem

; Co&ing< T%anslating t*e design into t*e atual system.

7 Testing< Does t*e system sol-e t*e (%oblem< 0a-e t*e %e=ui%ements been satis"ed< Does t*e system o%8 (%o(e%ly in all situations

7 Maintenance< ug "#es


4/45

(easi,ility Stu&y

Design

Co&ing

-nalysis8*e9uirements:

Testing


ORANGE IT SOLUTIONS

De"nes t*e on%ete st%ategy to enginee% some sota%e a%tiat

SD>C is se(a%ated into (*ases ?ste(s@ stages

S>DC also dete%mines t*e o%de% o t*e (*ases@ and t*e %ite%ia o%t%ansitioning %om (*ase to (*ase

. (easi,ility Stu&y;

The feasi,ility report

A((liations a%eas to be onside%ed egSto8 ont%ol@ (u%*asing@ Aounts et System in-estigations o% ea* a((liation Cost estimates System %e=ui%ements Timesale o% im(lementation+#(eted bene"ts

Page 4

T*e Analyst onduts an initialstudy o t*e (%oblem and as8s ist*e solution

Te*nologially (ossible+onomially (ossible>egally (ossibleB(e%ationally (ossible

si

b

le

!

"era

ti

on

ally

"

os

si

bl

e

S

.2 Systems -nalysis;

& System analysis and design is t*e (%oess o

& In-estigating a business.& $it* a -ie to dete%mining *o best to manage t*e -a%ious (%oedu%es andino%mation (%oessing tas8s t*at it in-ol-es.

.2. The Systems -nalyst

& 'e%o%ms t*e in-estigation..& and mig*t %eommend t*e use o a om(ute% tim(%o-e t*e eieny o t*e ino%mation systembeing in-estigated.

.2.2 Systems -nalysis

& T*e intention..& to dete%mine *o ell a business o(es it* itu%%ent ino%mation (%oessing needs@

& and *et*e% it is (ossible to im(%o-e t*e(%oedu%es ino%de% to ma8e it mo%e eient o%(%o"table.


5/45

(easi,ility Stu&y

Design

Co&ing

-nalysis

Testing


(easi,ility Stu&y

Design

Co&ing

-nalysis

Testing


ORANGE IT SOLUTIONS

Note: F,S ontains In(ut@ But(ut@ (%oess but no o%mat. se Cases ontains use% ation and system %es(onse it* "#ed

o%mat.

.! Systems Design;

& 'lanning t*e st%utu%e o t*e ino%mation system to beim(lemented.

& Systems analysis dete%mines *at t*e system should do

& and design dete%mines *o it should be done.

Page 5

hed#

le

d

time

sca

le

"

os

si

bl

e

ste

ms

a

naly

st

c

ond#

ct

s

an

in

it

ial

st

#d

yo

The System -nalysis *eport

,S?usiness ,e=ui%ement Doument F,S?Funtional ,e=ui%ement Doument B% Funtional s(ei"ations se Cases? se% ation and system ,es(onse

ET*ese 3 a%e t*e ase douments o% %iting Test Cases Doumenting t*e %esults

systems Go *a%ts data Go diag%ams o%gani9ation *a%ts %e(o%t


6/45

(easi,ility Stu&y

Design

Co&ing

-nalysis

Testing


ORANGE IT SOLUTIONS

System Design *eport

Design Doument t*at onsist o A%*itetu%al Design@ DatabaseDesign@ Inte%ae Design

." Co&ing;

Co&ing *eport

All t*e (%og%ams@ Funtions@ ,e(o%ts t*at %elated to Coding.

.' Testing;

Page 6

t

he

"ro

bl

em

and

a

s$

sis

t

he

sol

#t

io

n

Te

ch

no

logi

ca

ll

y

"o

ss

ib

le%

co

no

m

se% inte%ae designDesign o out(ut %e(o%tsIn(ut s%eensData sto%age ie "les@

database tablesSystem seu%ity

a8u(s@ -alidation@(asso%ds

Test (lan

(easi,ility Stu&y

Design

Co&ing

-nalysis

Testing


Program de'elo"ment%(#i"ment ac(#isition

)raft #" #ser g#ides

.'.


7/45

ORANGE IT SOLUTIONS

Testing is e#euting a (%og%am it* an indent o "nding +%%o%)Fault andFailu%e.Fault is a ondition t*at auses t*e sota%e to ail to (e%o%m its%e=ui%ed untion.+%%o% %ee%s to di7e%ene beteen Atual But(ut and +#(eted But(ut.Failu%e is t*e inability o a system o% om(onent to (e%o%m %e=ui%eduntion ao%ding to its s(ei"ation.Failu%e is an e-entH ault is a state o t*e sota%e@ aused by an e%%o%.


8/45

ORANGE IT SOLUTIONS

0

20

40

60

80

100

Cost

SDLC Phase

Cost of Defect Repair

% Cost 0 10 20 50 100

Require Design Coding Testing Custom

4ow e>actly Testing is &i?erent from @-A@CTesting is oten onused it* t*e (%oesses o =uality ont%ol and=uality assu%ane. Testing is t*e (%oess o %eating@ im(lementing ande-aluating tests.

Testing measu%es sota%e =uality.

Testing an "nd aultsH *en t*ey a%e %emo-ed@ sota%e =uality isim(%o-ed.

C is t*e (%oess o Ins(etions@ $al8!t%oug*s and ,e-ies.

A in-ol-es in Monito%ing and im(%o-ing t*e enti%e SD>C (%oess@ma8ing su%e t*at any ag%eed!u(on standa%ds and (%oedu%es a%eolloed@ and ensu%ing t*at (%oblems a%e ound and dealt it*.


9/45

ORANGE IT SOLUTIONS

measu%es =uality o-e% time and sta%ting %om a 8non base oe-aluation.

Too little emphasis on user tasBs!! beause teste%s ill ous on

ideal (at*s instead o %eal (at*s. $it* no time to (%e(a%e@ ideal (at*sa%e de"ned ao%ding to best guesses o% de-elo(e% eedba8 %at*e% t*anby a%eul onside%ation o *o use%s ill unde%stand t*e system o% *ouse%s unde%stand %eal!o%ld analogues to t*e a((liation tas8s. $it* notime to (%e(a%e@ teste%s ill be using a -e%y %est%ited set in(ut data@%at*e% t*an using %eal data ?%om use% ati-ity logs@ %om logialsena%ios@ %om a%eul onside%ation o t*e one(t domain.

Ine5cient over the long term!! =uality assu%ane in-ol-es a %ange otas8s. +7eti-e =uality assu%ane (%og%ams e#(and t*ei% base odoumentation on t*e (%odut and on t*e testing (%oess o-e% time@in%easing t*e o-e%age and g%anula%ity o tests o-e% time. %eat testing

%e=ui%es good test setu( and (%e(a%ation@ but suess it* t*e 8ind Test(lan!less a((%oa* des%ibed in t*is essay may %eino%e bad (%o:et andtest met*odologies. A ontinued (atte%n o =ui8!and!di%ty testing li8et*is is a sign t*at t*e (%odut o% a((liation is unsustainable in t*e long%un.

-reas of Testing;

lacB o> Testing

la8 bo# testing is also alled as Funtionality Testing. In t*is testinguse% ill be as8ed to test t*e o%%etness o t*e untionality it* t*e*el( o In(uts and But(uts. se% doesnKt %e=ui%e t*e 8noledge osota%e ode.

-pproach;E@)I%-ENCEC-SS;; Fo% ea* (iee o t*e s(ei"ation@ gene%ate one o% mo%e

e=ui-alene Class; >abel t*e lasses as LalidN o% LIn-alidN; ene%ate one test ase o% ea* In-alid +=ui-alene lass; ene%ate a test ase t*at Co-e%s as manyalid +=ui-alene Classes as (ossible

Equivalence partitioning(also called Equivalence Class Partitioningor ECP[1]) is

asoftware testingtechnique that divides the input data of a software unit into partitions of

equivalent data from which test cases can be derived. In principle, test cases are

designed to cover each partition at least once. This technique tries to define test cases

that uncover classes of errors, thereb reducing the total number of test cases that must

Page ,
http://en.wikipedia.org/wiki/Equivalence_partitioning#cite_note-1http://en.wikipedia.org/wiki/Software_testinghttp://en.wikipedia.org/wiki/Software_testinghttp://en.wikipedia.org/wiki/Software_testinghttp://en.wikipedia.org/wiki/Software_testinghttp://en.wikipedia.org/wiki/Equivalence_partitioning#cite_note-1


10/45

ORANGE IT SOLUTIONS

be developed. !n advantage of this approach is reduction in the time required for testing

a software due to lesser number of test cases.

"quivalence partitioning is tpicall applied to the inputs of a tested component, but ma

be applied to the outputs in rare cases. The equivalence partitions are usuall derived

from the requirements specification for input attributes that influence the processing ofthe test ob#ect.

Equivalence Class Testing

"$ Testing is when ou have a number of test items (e.g. values) that ou want to

test but because of cost (time%mone) ou do not have time to test them all.

Therefore ou group the test item into class where all items in each class are

suppose to behave e&actl the same. The theor is that ou onl need to test one of

each item to ma'e sure the sstem wor's.

Example 1

$hildren under ride the buss for free. oung people pa *1+, !dults *1 and -enior

$itien pa *.$lasses/

0rice/+ 2 !ge/+1

0rice/1+ 2 !ge/13

0rice/1 2 !ge/143

0rice/ 2 !ge/4infinit

Example 2 (more than one parameter)

$ellphones 56+, 743 and 73 run 7ava . 58+ and 788 run 7ava 4. 9ut there are two

possible browsers :ire:o& and ;pera, 7 models run :: and 5 models run ;.

$lasses/

9rowser/::, 7ava/ 2 0hones/743,73

9rowser/::, 7ava/4 2 0hones/7889rowser/;, 7ava/ 2 0hones/56+

9rowser/;, 7ava/4 2 0hones/58+

Dangers Of Equivalence Class Testing

There is a danger of using "$ Testing that is rarel mentioned in the testing boo's

but is ver important to remember.

Just e!ause t"o items#$alues are suppose to e in the same !lass and eha$e the

same% does not mean the& D' eha$e the same

That means that #ust because ou test one value in the class that !


11/45

ORANGE IT SOLUTIONS

0rice/1 2 !ge/143 ( 9oundar values 1, 43)

0rice/ 2 !ge/4infinit ( 9oundar values 4)

Critique of Boundary Value Testing

1) I, and other test professionals I have ta'en courses from, are not convinced that

most defects are hidden around the edges of each class. !nd I have never seen an

studies that proves this to be the case. ) The fact that ou need to use 9@ Testingproves that "$ Testing is flawed since ou test more than one value of each class. A)

It>s eas to use when using values li'e integers. 9ut what is a boundar value of

class of phones models or browsers versionsB

idden Boundary Value Testing

The boundar values of a class is often based on the specification of how the sstem

should wor'. This is all good and well but most sstems contain boundaries that are

not e&plained in an spec and ou will need to loo' for ourself. ".g. >Cow man

characters can I put into the test field before the sstem fails and brea's.>,>Cow big

can the data file become before it so slow to read it gets annoing>.

Real "orld examples

0asting one million characters into a te&t area in :ire:o& A. on win D crashes it

=e$aptcha has a limit of 14++A characters, does our sstem handle the 31A that itpasses bac' to it if somebod puts 14++3E characters in field. ;r does it brea'

Su!!ary

"$ Testing and 9@ Testing are great tools and ou should use them but the are not

perfect and don>t e&pect to find all defects using them. Fse our 'nowhow about the

sstem and our intelligence and intuition to tr more items and loo's for other was

it could fail. !nd loo' for the hidden boundaries?

oun&ary %alue -nalysis; ene%ate test ases o% t*e bounda%y -alues.

; Minimum alue @ Minimum alue O 1@ Minimum alue !1; Ma#imum alue@ Ma#imum alue O 1@ Ma#imum alue ! 1

Error uessing.Generating test cases against to the specification."hite Bo# Testing

$*ite bo# testing is also alled as St%utu%al testing. se% does %e=ui%et*e 8noledge o sota%e ode.

St%utu%e P 1 +nt%y O 1 +#it it* e%tain Const%aints@ Conditions and>oo(s.

$*y do *ite bo# testing *en *ite bo# testing is used to testono%mane to %e=ui%ementsQ

>ogi +%%o%s and ino%%et assum(tions most a%e li8ely to be made *ileoding o% Ls(eial asesN. Reed to ensu%e t*ese e#eution (at*s a%etested.

Page 11


12/45

(easi,ility Stu&y

Design

Co&ing

-nalysis

Testing


ORANGE IT SOLUTIONS

May "nd assum(tions about e#eution (at*s ino%%et@ and so ma8edesign e%%o%s.

Ty(og%a(*ial e%%o%s a%e %andom. ust as li8ely to be on an obsu%elogial (at* as on a mainst%eam (at*.

-pproach

asi 'at* TestingQ

Cylomati Com(le#ity and M Cabe Met*od

St%utu%e TestingQ

Condition Testing@ Data Flo Testing and >oo( Testing

rey o> Testing.

%ey bo# Testing is t*e ne te%m@ *i* e-ol-ed due to t*e di7e%entbe*a-io%s o t*e system. T*is is :ust a ombination o bot* la8 bo# &*ite bo# testing. Teste% s*ould *a-e t*e 8noledge o bot* t*einte%nals and e#te%nals o t*e untion.

+-en t*oug* you (%obably dont *a-e ull 8noledge o t*e inte%nalso t*e (%odut you test@ a test st%ategy based (a%tly on inte%nals is a(oe%ul idea. $e all t*is g%ay bo# testing. T*e one(t is sim(leQ I you8no somet*ing about *o t*e (%odut o%8s on t*e inside@ you antest it bette% %om t*e outside. T*is is not to be onused it* *ite bo#

testing@ *i* attem(ts to o-e% t*e inte%nals o t*e (%odut in detail. Ing%ay bo# mode@ you a%e testing %om t*e outside o t*e (%odut@ :ust asyou do it* bla8 bo#@ but you% testing *oies a%e ino%med by you%8noledge o *o t*e unde%lying om(onents o(e%ate and inte%at.

%ay bo# testing is es(eially im(o%tant it* $eb and Inte%neta((liations@ beause t*e Inte%net is built a%ound loosely integ%atedom(onents t*at onnet -ia %elati-ely ell!de"ned inte%aes. nlessyou unde%stand t*e a%*itetu%e o t*e Ret@ you% testing ill be s8indee(. 0ung Rguyens Testing A((liations on t*e $eb ?2UUU is a goode#am(le o g%ay bo# test st%ategy a((lied to t*e $eb.

1.6 Installation & Maintenance:

Page 12


13/45


14/45

ORANGE IT SOLUTIONS

V AnalysisV DesignV testingV Maintenane'%oblems it* ode!and!"# modelQ

1. Ate% se-e%al ite%ations@ ode beame -e%y (oo%ly st%utu%edHsubse=uent "#es beame -e%y e#(ensi-e2. +-en ell!designed sota%e oten -e%y (oo%ly mat*ed use%sK%e=ui%ementsQ e%e %e:eted o% needed to be %ede-elo(ed?e#(ensi-elyW3. C*anges to ode e%e e#(ensi-e@ beause o (oo% testing andmaintenane (%atiesSolutionsQ1. Design beo%e oding2. Requirements analysis beo%e design3. Se(a%ate testing and maintenance (*ases ate% oding

2.2.


15/45

ORANGE IT SOLUTIONS

V $ate%all model is a linear a((%oa*@ =uite inGe#ibleV At ea* (*ase@ eedba8 to (%e-ious (*ases is (ossible ?but isdisou%aged in (%atieV Still is t*e most widespread model today

'%oblems it* $ate%all ModelQ It doesnKt *a((en? ,e=ui%ements a%e %i99ed

,eal (%o:ets tend not to ollo a se=uential Go

Ati-ities a%e done o((o%tunistially du%ing all L(*asesN

Deli-e%y only at t*e end ?long ait

2.!. #rototyping mo&el;

V Int%odued to o-e%ome s*o%tomings o ate%all modelV Suitable to o-e%ome (%oblem o %e=ui%ements de"nitionV '%ototy(ing builds an operational model o t*e (lannedsystem@ *i* t*e ustome% an e-aluateMain (*asesQ1. ,e=ui%ements gat*e%ing2. ui8 design3. uild (%ototy(e4. Custome% e-aluation o (%ototy(e5. ,e"ne (%ototy(eIte%ate ste(s 4. and 5. to XtuneX t*e (%ototy(e6. +nginee% (%odut

+%%o%Q ,ee%ene sou%e not ound

Page 15


16/45

ORANGE IT SOLUTIONS

Mostly@ t*e (%ototy(e is disa%ded ate% ste( 5. and t*e atualsystem is built %om s%at* in ste( 6. ?throw-away prototyping)'ossible (%oblemsQV Custome% may ob:et to (%ototy(e being t*%on aay and maydemand Xa e *angesX to ma8e it o%8ing ?%esults in (oo%sota%e =uality and maintainabilityV Ine%io%@ tem(o%a%y design solutions may beome (e%manentate% a *ile@ *en t*e de-elo(e% *as o%gotten t*at t*ey e%e

only intended to be tem(o%a%y ?%esults in (oo% sota%e =uality2." Incremental;Du%ing t*e "%st one!mont* (*ase@ t*e de-elo(ment team o%8ed%om stati -isual designs to ode a (%ototy(e. In ous g%ou(meetings@ t*e team disussed use%sK needs and t*e (otentialeatu%es o t*e (%odut and t*en s*oed a demonst%ation o its(%ototy(e. T*e e#ellent eedba8 %om t*ese ous g%ou(s *ad ala%ge im(at on t*e =uality o t*e (%odut.Main (*asesQ1. De"ne outline %e= ui%ements2. Assign %e=ui%ements to in%ements

3. Design system a%*itetu%e4. De-elo(5. Integ%ate6. alidate


Page 16


17/45

ORANGE IT SOLUTIONS

Ate% t*e seond g%ou( o ous g%ou(s@ t*e eatu%e set as%o9en and t*e (%odut de"nition om(lete. Im(lementationonsisted o ou%!to!si#!ee8 yles@ it* sota%e deli-e%ed o%beta use at t*e end o ea* yle. T*e enti%e %elease too8 1U

mont*s %om de"nition to manuatu%ing %elease. Im(lementationlasted 4.5 mont*s. T*e %esult as a o%ld!lass (%odut t*at *ason many aa%ds and *as been easy to su((o%t.

2.' Spiral mo&el;V Bb:eti-eQ o-e%ome (%oblems o ot*e% models@ *ileombining t*ei% ad-antagesV Yey om(onentQ %is8 management ?beause t%aditional modelsoten ail *en %is8 is negletedV De-elo(ment is done incrementally@ in se-e%al cyclesV Cyle asoten as neessa%y to "nis*

Main (*asesQ1. Dete%mine ob:eti-es@ alte%nati-es o% de-elo(ment@ andonst%aints o% t*e (o%tion o t*e *ole system to bede-elo(ed in t*e u%%ent yle2. +-aluate alte%nati-es@ onside%ing ob:eti-es andonst%aintsH identiy and %esol-e %is8s3. De-elo( t*e u%%ent yles (a%t o t*e system@ usinge-olutiona%y o% on-entional de-elo(ment met*ods?de(ending on %emaining %is8sH (e%o%m -alidation att*e end4. '%e(a%e (lans o% subse=uent (*ases


Page 1*


18/45


19/45

ORANGE IT SOLUTIONS

!. System Stu&y;

Ma8ing douments o. Domain Hnowle&ge ;sed to 8no about t*e lient business

an8ing ) Finane ) Insu%ane ) ,eal!estates ) +,' ) C,M ) Bt*e%s

2. Software ; F%ont +nd ?I C ) AA) FB,MS ) %ose%'%oess >anguage it* e ant to %ite (%og%ammesa8 +nd Database li8e B%ale@ S> Se%-e% et.

!. 4ar&ware; Inte%net) Int%anet) Se%-e%s *i* you ant to install.

". (unctional #oints; Ten >ines B Code ?>BC P 1 Funtional'oint.

'. Num,er of #ages; T*e doument *i* you ant to (%e(a%e.

+. Num,er of *esources ; >i8e '%og%amme%s@ Designe%s@ andManage%s.

/. Num,er of Days; Fo% atual om(letion o t*e '%o:et.

0. Num,ers of Mo&ules

1. #riority; 0ig*) Medium) >o im(o%tane o% Modules

!.2 ScopeA -pproachA Estimation;

Scope; $*at to be tested$*at not to test

-pproach; Testing >ie CyleEstimation; ?Fo%mula P >BC) F'),esou%es

1UUU P 1UU F' ?1U >BC P 1 F'

Page 1,


20/45

ORANGE IT SOLUTIONS

1UU Z3 P 3UU ?F' Z3 T+C0. P T+STCAS+S T0+3 T+C0A,+

1. +IA>+RC+C>ASSQ2. ounda%y alue Analysis3. +%%o% uessing.

3U TC 'a% Day P[ 3UU)3U P 1U Days to Design Test Cases

Test Case ,e-ie P[ \ o Test Case Design ?5 Days Test Case +#eution P 1 \ o Test Case Design?15 Days

Deet 0eadlining P Test Case Design ?5 Days

Test 'lan P 5 days ? 1 ee8

u7e% Time P 25] o +stimation

!.! Test #lan Design;T*e Test 'lan Design doument *el(s in test e#eution it ontain

1. About t*e lient and om(any2. ,ee%ene doument ?,S@ F,S and I et.3. So(e ?$*at to be tested and *at not to be 4. B-e%-ie o A((liation5. Testing a((%oa* ?Testing st%ategy

6. Fo% ea* testing De"nition

Taoni

Sta%t %ite%ia

Sto( %ite%ia/. ,esou%es and t*e%e ,oles and ,es(onsibilities. Deet de"nition. ,is8 ) Contingeny ) Mitigation 'lan1U. T%aining ,e=ui%ed11. S*edules12. Deli-e%ables

!." Test Cases Design;


21/45

o through the )se cases (unctional Spec

Su,mit the *eview *eport

Try to Fn& the gap ,etween TC )se cases

TaBe checBlist

TaBe a &emo of functionally

ORANGE IT SOLUTIONS

Test ases de-elo(ed o% untionality testing an be used o%Integ%ation)System),eg%ession testing and (e%o%mane testingit* e modi"ations.in8sN-re there any issues to ,e consi&ere&6es there are few Issues;All t*e TCKs s*ould be t%aeable.T*e%e s*ould not be too many du(liate test ases.But dated test ases s*ould be lea%ed o7.All t*e test ases s*ould be e#eutable.

TC ID #re

Con&itionDescription E>pecte&

*esult-ctual*esult

Status

*emarBs

ni=ueTestCasenumbe%

Conditiontosatis"ed

1. $*at tobe tested

2. *at datato(%o-ided

3. *atation tobe done

As (ea%FS,

System%es(onse

'ass o%Fail

I any

Ja*oo!UU1

Ja*ooeb (ages*oulddis(layed

1. C*e8inbo# isdis(layed

2. se%ID)'$

3. Cli8 onSubmit

Systems*ouldmail bo#

System%es(onse

!.' Test Case *eview;

'ee% to (ee% ,e-ies

Team >ead ,e-ieTeam Manage% ,e-ie

*eview #rocess

Page 21


22/45

ChecB the availa,ility of application

Implement the Test Cases

TaBe the Test Case &ocument

ORANGE IT SOLUTIONS

*eview (ormat

*eviewID Origin Description Status

#riority

ni=ue ID i%t* (laeF%om *e%eit sta%ts

Deetdes%i(tion B(en)Close Ma:o%MediumMino%

!.+ Test Case E>ecution;

E#eution and e#eution %esults (lays a -ital %ole in t*etesting. +a* and e-e%y ati-ity s*ould *a-e (%oo.

T*e olloing ati-ities s*ould be ta8en a%eQ1. Rumbe% o test ases e#euted.

2. Rumbe% o deets ound3. S%een s*oots o suessul and ailu%e e#eutionss*ould be ta8en in o%d doument.4. Time ta8en to e#eute.5. Time asted due to t*e una-ailability o t*e system.

Test Case E>ecution #rocess;

Page 22


23/45


24/45

ORANGE IT SOLUTIONS

Page 24

%-I

D

Defect Closer

Defect -ccepte&

Defect *aise&

Defect (i>e&

Internal Defect*eview

Defect Su,mitte& toDev Team

%-ID

Defect*eJecte&

Defect*eJecte&


25/45

ORANGE IT SOLUTIONS

Ro

Types of Defects

Cosmeti GaData o%%u(tionData lossDoumentation IssueIno%%et B(e%ationInstallation '%oblemMissing Featu%eSlo 'e%o%maneSystem C%as*ne#(eted e*a-io%n%iendly be*a-io%

4ow &o u &eci&e the Severity of the &efect

Se-e%ity>e-el

Des%i(tion ,es(onse Time o% Tu%n!a%oundTime

0ig* A deet ou%%ed due to t*einability o a 8ey untion to(e%o%m. T*is (%oblem ausest*e system *ang it *alts?%as*@ o% t*e use% is d%o((edout o t*e system. Animmediate "# o% o%8 a%oundis needed %om de-elo(mentso t*at testing an ontinue.

Deet s*ould be %es(onded toit*in 24 *ou%s and t*esituation s*ould be %esol-edtest e#it

Page 25


26/45

ORANGE IT SOLUTIONS

A deet ou%%ed *i*se-e%ely %est%its t*e systemsu* as t*e inability to use ama:o% untion o t*e system.T*e%e is no ae(table o%8!

a%ound but t*e (%oblem doesnot in*ibit t*e testing o ot*e%untions

A %es(onse o% ation (lans*ould be (%o-ided it*in 3o%8ing days and t*e situations*ould be %esol-ed beo%e teste#it.

>o A deet is ou%%ed *i*(laes mino% %est%it on auntion t*at is not %itial.T*e%e is an ae(table o%8!a%ound o% t*e deet.

A %es(onse o% ation (lans*ould be (%o-ided it*in 5o%8ing days and t*e situations*ould be %esol-ed beo%e teste#it.

Bt*e%s An inident ou%%ed *i*

(laes no %est%itions on anyuntion o t*e system. Roimmediate im(at to testing.

A Design issue o%,e=ui%ements not de"niti-elydetailed in (%o:et.

T*e "# dates a%e sub:et tonegotiation.

An ation (lan s*ould be

(%o-ided o% ne#t %elease o%utu%e en*anement

Defect Severity %S Defect #riority

T*e ene%al %ule o% t*e "#ing t*e deets ill de(end on t*eSe-e%ity. All t*e 0ig* Se-e%ity Deets s*ould be "#ed "%st.T*is may not be t*e same in all ases some times e-ent*oug* se-e%ity o t*e bug is *ig* it may not be ta8e as t*e0ig* (%io%ity.At t*e same time t*e lo se-e%ity bug may be onside%ed as*ig* (%io%ity.

Defect TracBing Sheet

DefectNo

Description

Origin Severity #riority Status

Page 26


27/45

ORANGE IT SOLUTIONS

ni=ueRo

De o ug i%t*(lae ot*e ug

C%itialMa:o%MediumMino%Cosmeti

0ig*Medium

>o

Submitted

Ae(tedFi#ed

,e:eted

'ost(onedClosed

Defect TracBing Tools

ug T%a8e% !! S> '%o(%ieta%y Tools

,ational Clea% uestTest Di%eto%

!.0 ap -nalysis;

1. ,S s S,S,SU1 < S,SU1

!S,SU2 !S,SU3

2. S,S s TCS,SU1 < TCU1

! TCU2 ! TCU3

3. TC s DeetsTCU1 < DeetsU1

< DeetsU2!.1 Delivera,les;

" Testing #hases $ The % Mo&el

e%i"ation Stati System < Doing ,ig*t ob

alidation Dynami System ! ob ,ig*t

Page 2*

usiness*e9uirements

%eriFcation

Software*e9uirements

%eriFcation

DesignSystem

%eriFcation

uil&System

%eriFcation

)nitTest

%ali&ation

IntegrationTest

%ali&ation

SystemTest

%ali&ation

-cceptanceTest

%ali&ation


28/45

ORANGE IT SOLUTIONS

". )nit Testing;In nit testing use% is su((osed to *e8 ea* and e-e%y mi%ountion. All "eld le-el -alidations a%e e#(eted to test at t*estage o testing.In most o t*e ases De-elo(e% ill do t*is.

-pproach;

E@)I%-ENCEC-SS;; Fo% ea* (iee o t*e s(ei"ation@ gene%ate one o% mo%ee=ui-alene Class; >abel t*e lasses as LalidN o% LIn-alidN; ene%ate one test ase o% ea* In-alid +=ui-alene lass; ene%ate a test ase t*at Co-e%s as manyalid +=ui-alene Classes as (ossible

oun&ary %alue -nalysis; ene%ate test ases o% t*e bounda%y -alues.; Minimum alue @ Minimum alue O 1@ Minimum alue !1

; Ma#imum alue@ Ma#imum alue O 1@ Ma#imum alue ! 1

Error uessing.< ene%ating test ases against to s(ei"ation

".2 Integration Testing;

Page 2+


29/45

ORANGE IT SOLUTIONS

T*e (%ima%y ob:eti-e o integ%ation testing is to diso-e% e%%o%sin t*e inte%aes beteen Modules)Sub!Systems ?0ost & ClientInte%aes.

-pproach;

TopDown -pproach

T*e integ%ation (%oess is (e%o%med in a se%ies o 5 ste(s1. T*e main ont%ol module is used as a test d%i-e%@ and stubs

a%e substituted o% all modules di%etly subo%dinate to t*emain ont%ol module.

2. De(ending on t*e integ%ation a((%oa* seleted ? de(t* o%b%eadt*!"%st subo%dinate stubs a%e %e(laed at a time it*atual modules.

3. Tests a%e onduted as ea* module is module isinteg%ated.

4. Bne om(letion o ea* set o tests@ anot*e% stub is%e(laed it* t*e %eal!module.

5. ,eg%ession testing may be onduted to ensu%e t*at nee%%o%s *a-e not been int%odued.

ottom)p -pproach.

- bottom!u( integ%ation st%ategy may be im(lemented it* t*eolloing ste(sQ

1. >o le-el modules a%e ombined into luste%s ?Some timesalled builds t*at (e%o%m a s(ei" sota%e sub untion.

2. A d%i-e% ? ont%ol (%og%am o% testing is %itten tooo%dinate test ase in(ut and out(ut.

3. T*e luste% is tested.4. D%i-e%s a%e %emo-ed and luste%s a%e ombined u(a%d in

t*e (%og%am st%utu%e

An integ%ation testing is onduted@ t*e teste% s*ould identiy%itial modules. A %itial module *as one o% mo%e o t*eolloing *a%ate%istisQ

1. Add%ess se-e%al sota%e %e=ui%ements.2. 0as a *ig*!le-el o ont%ol. ?%esides %elati-ely *ig* in t*e

(%og%am st%utu%e3. Com(le# & +%%o%!'*one.4. 0a-e de"nite (e%o%mane %e=ui%ements.

".! System Testing;

Page 2,


30/45

ORANGE IT SOLUTIONS

T*e (%ima%y ob:eti-e o system testing is to diso-e% e%%o%s*en t*e system is tested as a *ole. System testing is also alledas +nd!+nd Testing. se% is e#(eted to test %om >ogin!To!>ogoutby o-e%ing -a%ious business untionalities.

-pproach;IDO Mo&el

Identiying t*e +nd!+nd)usiness >ie Cyles.Design t*e test and data.O(timi9e t*e +nd!+nd)usiness >ie Cyles.

"." -cceptance Testing;

T*e (%ima%y ob:eti-e o ae(tane testing is to get t*eae(tane %om t*e lient. Client ill be using t*e systemagainst t*e business %e=ui%ements.

'%e!use% ae(tane testing ill be onduted to ase%tain t*estability and to *e8 *et*e% t*e om(lete untionality o t*esystem is *e8ed du%ing system testing. Ate% t*e "%st %ound osystem testing@ test enginee%s ill go t*%oug* t*e test ases?Test S%i(ts sent by t*e use%s. T*ey ill ase%tain *et*e% a(a%tiula% ondition ?untionality is o-e%ed and t*e test asenumbe% ill be ente%ed against ea* ondition. I a (a%tiula%ondition test ase sent by t*e use% is not o-e%ed beause ot*e *anges in t*e %e=ui%ement@ t*at (a%tiula% test ase ill bedoumented ?%ee% t*e tabula% o%mat and t*e e#isting be*a-io%

o t*e system ill be mentioned in t*e %ema%8s olumn.$*en a (a%tiula% ondition is not o-e%ed@ a ne test ase is(%e(a%ed along it* t*e test data and it is e#euted to ensu%et*e system is o%8ing ao%dingly. I t*e%e a%e any test ases*i* a%e not o-e%ed du%ing system testing and *en t*e%e isno su((o%ti-e doument o% t*at (a%tiula% test ase it is namedas an in-alid test ase. Ate% t*e ma((ing t*e *ole doumentill be sent ba8 to t*e use%.-pproach; E

uilding a team it* %eal!time use%@ untional use%s andde-elo(e%s.

+#eution o business Test Cases.


31/45

ORANGE IT SOLUTIONS

(reeKe uil&usiness*e9uirementsDocs

Ae(tane TestCases

Ae(taneTesting

Software

*e9uirementsDocs

System Test

Cases

System testing

Design*e9uirementsDocs

Integ%ation testCases

Integ%ationTesting

Co&e nit Test Cases nit Testing

' Testing Metho&s $ ()**#SC Mo&el

'. (unctionality Testing;O,Jective;

. Test against system re9uirements.

2. To conFrm all the re9uirements are covere&.-pproach;E@)I%-ENCEC-SSoun&ary %alue -nalysisError uessing.

'.2 )sa,ility Testing;To test the Easiness an& )serfrien&liness of the system.-pproach;@ualitative @uantitative

@ualitative -pproach;

. Ea* and e-e%y untion s*ould a-ailable %om all t*e(ages o t*e site.

2. )se% s*ould able to submit ea* and e-e%y %e=uest it* in4!5 ations.

!. Con"%mation message s*ould be dis(layed o% ea* ande-e%y submit.

@uantitative -pproach;4euristic ChecBlist s*ould be (%e(a%ed it* all t*e gene%al testases t*at all unde% t*e lassi"ation o *e8ing.T*is gene%i test ases s*ould be gi-en to 1U di7e%ent (eo(leand as8 to e#eute t*e system to ma%8 t*e (ass)ail status.T*e a-e%age o 1U di7e%ent (eo(le s*ould be onside%ed as t*e"nal %esult.E>ample; Some (eo(lemay eelsystem is mo%e use%s %iendly@I t*e submit is button on t*e let side o t*e s%een. At t*e same

Page 31


32/45

ORANGE IT SOLUTIONS

time some ot*e% may eel its bette% i t*e submit button is (laedon t*e %ig*t side.

ClassiFcation of ChecBing;Cla%ity o ommuniation.

AessibilityConsistenyRa-igationDesign & Maintenaneisual ,e(%esentation.

'.! *elia,ility Testing;

*T is (%o(e%ty@ *i* de"nes *o ell t*e sota%e meets its%e=ui%ements.Bb:eti-e is to "nd Mean Time beteen ailu%e)time a-ailable

unde% s(ei" load (atte%n. Mean time o% %eo-e%y.

-pproach; **T8*ational *eal Time: for continuous hoursof operation.More then 0'= of the sta,ility is must.*elia,ility Testing helps you to conFrm;usiness logi (e%o%ms as e#(etedAti-e buttons a%e %eally ati-eCo%%et menu o(tions a%e a-ailable,eliable *y(e% lin8s

?$*y is load %unne% used o% %eliability testing !%easoni%tual se%s an be %eated using >oad ,unne%. >oad Sene%ios@*i* a%e a mi# o business@ (%oesses and t*e numbe% o -i%tualuse%s@ ill %un on ea* load se%-e%. se% an =ui8ly om(osemulti!use% test sena%ios using >oad ,unne%Ks Cont%olle%.T*eCont%olle%Ks inte%ati-e a(ability (%o-ides an inte%ati-een-i%onment in *i* use% an manage and d%i-e t*e load testsena%io@ as ell as %eate %e(eatable and onsistent load. >oad,unne%Ks g%a(*ial inte%ae *el(s to o%gani9e and ont%olsena%ios du%ing load test setu( and e#eution.?$%ite some

sentenes t*at an be o%%elated it* load %unne%. Reed to (utt*is sentene in an a((%o(%iately

'." *egression Testing;Bb:eti-e is to *e8 t*e ne untionalities *as ino%(o%atedo%%etly it* out ailing t*e e#isting untionalities.

Page 32


33/45

ORANGE IT SOLUTIONS

,AD < In ase o ,a(id A((liation de-elo(ment ,eg%ession Test(lays a -ital %ole as t*e total de-elo(ment *a((ens in bits and(iees.T*e te%m X%eg%ession testingX an be a((lied to ays. Fi%st@*en a ode (%oblem *as been "#ed@ a %eg%ession test %uns tests

to -e%iy t*at t*e deet is in at "#ed.H XImagine "nding ane%%o%@ "#ing it@ and %e(eating t*e test t*at e#(osed t*e (%oblemin t*e "%st (lae. T*is is a %eg%ession testX. Seond@ %eg%essiontesting is t*e ounte%(a%t o integ%ation testingQ *en ne odeis added to e#isting ode@ %eg%ession testing -e%i"es t*at t*ee#isting ode ontinues to o%8 o%%etly@ *e%eas integ%ationtesting -e%i"es t*at t*e newode o%8s as e#(eted. ,eg%essiontesting an des%ibes t*e (%oess o testing ne ode to -e%iyt*at t*is ne ode *asnt b%o8en any old ode

-pproachQ Automation tools

'.' #erformance Testing;

#%ima%y ob:eti-e o t*e (e%o%mane testing is Lto demonst%atet*e system o%8s untions as (e% s(ei"ations it* in gi-en

%es(onse time on a (%odution si9ed database.Bb:eti-esQAssessing t*e system a(aity o% g%ot*.Identiying ea8 (oints in t*e a%*itetu%eDetet obsu%e bugs in sota%eTuning t*e systeme%iy %esiliene & %eliability

'e%o%mane 'a%amete%sQ,e=uest!,es(onse TimeT%ansations (e% Seond

Tu%n A%ound time'age don load timeT*%oug* 'ut

-##*O-C4; )S-EO(-)TOM-TIONTOOSClassiFcation of #erformance Testing;oa& Test%olume Test

Page 33


34/45

ORANGE IT SOLUTIONS

Stress Test

oa& Testing-pproach; oa& #roFle

%olume Testing-pproach; Data #roFle

Stress Testing-pproach; *C@E -pproach

*e(eatedly o%8ing on t*e same untionalityC%itial @ue%y +#eution ?oin ue%iesTo Emulate (ea8 load.oa& %s Stress;$it* t*e Sim(le Sena%io ?Funtional ue%y@ R numbe% o (eo(le

o%8ing on it ill not eno%e st%ess on t*e se%-e%.A om(le# sena%io it* e-en one less numbe% o use%s illst%ess t*e se%-e%.'.+ Scala,ility Testing;O,Jective is to Fn& the ma>imum num,er of user systemcan han&le.

ClassiFcation;NetworB Scala,ilityServer Scala,ility-pplication Scala,ility

-pproach; #erformance Tools

'./ Compati,ility Testing;

Com(atibility testing (%o-ides a basi unde%standing o *o a(%odut ill (e%o%m o-e% a ide %ange o *a%da%e@ sota%e &neto%8 on"gu%ation and to isolate t*e s(ei" (%oblems.-pproach; ET -pproach

En-i%onment Seletion.

T+ST+DC,+ATIBR

I. Selection of environment

T*e%e a%e many ty(es o B(e%ating systems@ %ose%s@ Ms usedby ide %ange o audiene a%ound t*e o%ld. Com(atibilitytesting o% all t*ese (ossible ombinations is e#*austi-e and

Page 34


35/45

ORANGE IT SOLUTIONS

*ene@ o(timi9ing t*e ombination o en-i%onment is -e%y%itial.

Many times t*e ustome% may gi-e t*e en-i%onment details o%t*e om(atibility testing. Inase i it is not gi-en@ t*e olloing

st%ategy may be ado(ted o% seleting t*e en-i%onment.

y un&erstan&ing the en& users.

>ist t*e (ossible end use%s o% t*e (%o(osed sota%e a((liationto be tested. Analy9e t*ei% %e=ui%ement o en-i%onment on t*ebasis o t*e (%e-ious e#(e%iene ?,egion ise o% ty(e o t*ea((liation. Selet t*e (ossible ombination o o(e%ating system& b%ose% %om t*is in(ut.

Importance of selecting ,oth ol& ,rowser an& new

,rowsers

Many end use%s use t*e deault b%ose%@ *i* a%e (a%t o t*eo(e%ating system & may not u(g%ade o% ne -e%sions. $*e%e assome end!use%s may tend to go o% t*e latest -e%sions o t*eb%ose%s. 0ene im(o%tane s*ould be gi-en o% bot* old & ne-e%sions o t*e b%ose%s o% om(atibility testing.

Selection of the Operating System

T*e o(e%ating system o Mi%osot *as ide %ange o use%om(a%ed to ot*e% o(e%ating system. 0oe-e% many also useMaintos* and ni# o(e%ating system. T*e om(atibility o t*ea((liation it* di7e%ent o(e%ating system is -e%y im(o%tant.T*e details o o(e%ating system -e%sus b%ose%s su((o%ted a%egi-en -ide Table!3 o setion 2.U.

II. Test e& Creation

Folloing ste(s a%e ado(ted o% %eation o test bed o% di7e%ent-e%sion o b%ose%s and Mi%osot o(e%ating system. T*is(%oedu%e is not a((liable o% Maintos* and ni# o(e%ating

systems.

$*en t*e use% ants to loo8 o% om(atibility on di7e%entMi%osot o(e%ating systems and di7e%ent -e%sion o b%ose%s@olloing ste(s *el(s to %edue time and ost.

1 'a%tition o t*e *a%d dis8.2 C%eation o ase Image

Page 35


36/45

ORANGE IT SOLUTIONS

: #artition of the har& &isB

'a%tition *el(s in installing mo%e t*an one o(e%ating systemon a single *a%d dis8. 0a%d dis8 is a-ailable it* to (a%tition

namely (%ima%y (a%tition and e#tended (a%tition. T*e "%stseto% o *a%d dis8 ontains a (a%tition table. T*is (a%titiontable *as %oom to des%ibe ou% (a%titions t*ese a%e alled(%ima%y (a%titions. Bne o t*ese (%ima%y (a%titions an (ointto a *ain o additional (a%titions. +a* (a%tition in t*is *ainis alled a logial (a%tition & one (a%tition is -isible at a time.

sing (a%tition magi sota%e t*e (%ima%y (a%tition o t*e*a%d dis8 an be on"gu%ed into ma#imum o ou% (a%ts.

Folloing a%e t*e ste(s in-ol-ed *ile (a%titioningQa C%eate one (%ima%y (a%tition o %e=ui%ed si9e.b Ma8e it ati-e. >oad t*e (a%tiula% o(e%ating system.d sing (a%tition magi *ide t*at (a%tition.e Ate% installing ea* o(e%ating system ste(s a@ b@ @ d

a%e %e(eated.

$it* t*is t*e (%ima%y (a%tition o t*e *a%d dis8 an beon"gu%ed it* $inRT@ $in5@$in & $in28 %es(eti-ely.

2: Creation of ase Image

ase image is a lone o *a%d dis8. It is (ossible to %eate t*ebase image o all t*e ou% o(e%ating system o Mi%osotalong it* I+ loe% -e%sion and oe /.

Inase o Inte%net +#(lo%e%@ it is not (ossible to *ange %om*ig*e% -e%sion to loe% -e%sion. $it* t*e *el( o base imageit is (ossible to %e%ite t*e *a%d dis8 it* t*e %e=ui%edB(e%ating system@ *i* ontains loe% -e%sion o I+. Ro%ton

g*ost sota%e *el(s to ta8e t*e base image o t*e(a%titioned *a%d dis8 along it* t*e %e=ui%ed o(e%atingsystem.Inase o Retsa(e Ra-igato% t*e%e is no (%oblem o *anging%om *ig*e% -e%sion to loe% -e%sion and -ie -e%sa.Folloing is t*e om(a%ison o t*e time %e=ui%ed o% installingo(e%ating systems it* & it*out Ro%ton g*ost.

Page 36


37/45

ORANGE IT SOLUTIONS


38/45

ORANGE IT SOLUTIONS

+." oa&Tests;T*is ty(e o test is done to test t*e ebsite using t*e load t*att*e ustome% e#(ets to *a-e on *is site. T*is is somet*ing li8e aL%eal o%ld testN o t*e ebsite.Fi%st e *a-e to de"ne t*e ma#imum %e=uest times e ant t*e

ustome%s to e#(e%iene@ t*is is done %om t*e business andusability (oint o -ie@ not %om a te*nial (oint o -ie. At t*is(oint e need to alulate t*e im(at o a slo ebsite on t*eom(any sales and su((o%t osts.T*en e *a-e to alulate t*e antii(ated load and load (atte%no% t*e ebsite ?,ee% Anne#u%e I o% details on load alulation*i* e t*en simulate using t*e Tool.At t*e end e om(a%e t*e test %esults it* t*e %e=uests timese anted to a*ie-e.

+.' StressTests;

T*ey simulate b%ute o%e atta8s it* e#essi-e load on t*e ebse%-e%. In t*e %eal o%ld situations li8e t*is an be %eated by amassi-e s(i8e o use%s < a% abo-e t*e no%mal usage < e.g.aused by a la%ge %ee%%e% ?imagine t*e ebsite being mentionedon national T.T*e goals o st%ess tests a%e to lea%n unde% *at load t*e se%-e%gene%ates e%%o%s@ *et*e% it ill ome ba8 online ate% su* amassi-e s(i8e at all o% %as* and *en it ill ome ba8 online.+.+ oad,unne% %om Me%u%y Inte%ati-e

Ast%a>oad %om Me%u%y Inte%ati-e

Sil8 'e%o%me% %om Segue

,ational Suite Test Studio %om ,ational

Page 3+


39/45

ORANGE IT SOLUTIONS

,ational Site >oad %om ,ational

B(enSTA %om Cy%ano

$ebload %om ,ad-ie

,S$ eSuite %om +m(i%i#

MS St%ess tool %om Mi%osot

+.0 #erformance Test #rocess;This is a general process for performance Testing. This process can becustomied according to the pro#ect needs. :ew more process steps can beadded to the e&isting process, deleting an of the steps from the e&istingprocess ma result in Incomplete process. If $lient is using an of the tools,In this case one can blindl follow the respective process demonstrated bthe tool.

eneral #rocess Steps;

Setting up of the test environment

Page 3,

Setting up of the

Environment

Record & Playback in

the standby mode

Enhancement of the

script to support

multiple users

Configure the scripts

Execution for fixed

users and reporting

the status to the

developers

Reexecution of the

scenarios after the

developers finetune

the code


40/45

ORANGE IT SOLUTIONS

T*e installation o t*e tool@ agents@ di%eto%y st%utu%e%eation o% t*e sto%age o t*e s%i(ts and %esults andinstallation additional sota%e i essential to ollet t*ese%-e% statistis ?li8e SRM' agent. It is also essential to

ensu%e t*e o%%etness o t*e en-i%onment by im(lementingt*e d%y %un.

*ecor& play,acB in the stan& ,y mo&eT*e s%i(ts a%e gene%ated using t*e s%i(t gene%ato% and(layed ba8 to ensu%e t*at t*e%e a%e no e%%o%s in t*e s%i(t.

Enhancement of the script to support multiple usersT*e -a%iables li8e logins@ use% in(uts et. s*ould be(a%amete%ised to simulate t*e li-e en-i%onment. It is alsoessential sine in some o t*e a((liations no to use%s an

login it* t*e same id.

ConFguration of the scenariosSena%ios s*ould be on"gu%ed to %un t*e s%i(ts on di7e%entagents@ s*edule t*e sena%ios@ dist%ibute t*e use%s ontodi7e%ent s%i(ts@ ollet t*e data %elated to database et.

0ostsT*e ne#t im(o%tant ste( in t*e testing a((%oa* is to %un t*e-i%tual use%s on di7e%ent *ost ma*ines to %edue t*e load ont*e lient ma*ine by s*a%ing t*e %esou%es o t*e ot*e%

ma*ines. se%sT*e numbe% o use%s *o need to be ati-ated du%ing t*ee#eution o t*e sena%io. Sena%iosA sena%io mig*t eit*e% om(%ise o a single s%i(t o% multi(les%i(ts. T*e main intention o %eating a sena%io to simulateload on t*e se%-e% simila% to t*e li-e)(%odution en-i%onment. ,am(ingIn t*e li-e en-i%onment not all t*e use%s login to t*ea((liation simultaneously. At t*is stage e an simulate t*e-i%tual use%s simila% to t*e li-e en-i%onment by deiding !

. 0o many use%s s*ould be ati-ated at a (a%tiula%(oint o time as a bat*

2. $*at s*ould be t*e time inte%-al beteen e-e%ybat* o use%s

Page 4-


41/45

ORANGE IT SOLUTIONS

E>ecution for F>e& users an& reporting the status tothe &evelopersT*e s%i(t s*ould be initially e#euted o% one use% and t*e%esults)in(uts s*ould be -e%i"ed to *e8 it out *et*e% t*ese%-e% %es(onse time o% a t%ansation is less t*an o% e=ual to

t*e ae(table limit ?ben* ma%8.I t*e %esults a%e ound ade=uate t*e e#eution s*ould beontinued o% di7e%ent set o use%s. At t*e end o e-e%ye#eution t*e %esults s*ould be analysed.

I a stage %ea*es *en t*e time ta8en o% t*e se%-e% to%es(ond to a t%ansation is abo-e t*e ae(table limit@ t*ent*e in(uts s*ould be gi-en to t*e de-elo(e%s.

*ee>ecution of the scenarios after the &evelopers Fnetune the co&e

Ate% t*e "ne!tuning@ t*e sena%ios s*ould be %e!e#euted o%t*e s(ei" set o use%s o% *i* t*e %es(onse asinade=uate. I ound satisato%y@ t*en t*e e#eution s*ouldbe ontinued until t*e deided load.(inal reportAt t*e end o t*e (e%o%mane testing@ "nal %e(o%t s*ould begene%ated *i* s*ould om(%ise o t*e olloing

Documents

Testing Details