typesoftesting-130623074510-phpapp01

7/24/2019 typesoftesting-130623074510-phpapp01

1/27

Types Of Testing

Presented By:

Sonam Agarwal3irdyear, IT


2/27

Introduction & Fundamentals

What is Software Testing?

Why testing is necessary?

Who does the testing?What do we test?


3/27

Error ,Bug ,Fault ,Failure

A person makes an Error That creates a faultin software That can cause a failure inoperation Bug, Fault & Failure.

Error :An error is a human action thatproduces the incorrect result.

Bug : The presence of error at the time of

execution of the software.Fault : State of software caused b an error.

Failure : !e"iation of the software from itsexpected result.


4/27

Objectives of testing

The aim of the testing is to identify all defectsexisting in a software prodct! It is not possi"leto garantee that the software is error free! Thisis "ecase of the fact that the inpt data domain

of most software prodcts is #ery large!A good test case is one that has a high

pro"a"ility of $nding an as%yet%ndisco#erederror!

A sccessfl test is one that nco#ers an as%yet%ndisco#ered error!Wat testing cannot do !o &annot show the a"sence of errors!


5/27

Objectives of a "oft#areTester

'ind "gs as early as possi"le and ma(e srethey get $xed!

To nderstand the application well!

Stdy the fnctionality in detail to $nd wherethe "gs are li(ely to occr!

Stdy the code to ensre that each and e#eryline of code is tested!

&reate test cases in sch a way that testing isdone to nco#er the hidden "gs and alsoensre that the software is sa"le and relia"le!


6/27

$eri%cation & $alidation

$eri%cation% refers to the set of acti#itiesthat ensre that software correctlyimplements a speci$c fnction!

$alidationrefers to a di)erent set ofacti#ities that ensre that the software thathas "een "ilt is tracea"le to cstomerre*irements!

#eri$cation%Are we building the productright'

#alidation%Are we building the right product'


7/27

Testing $s 'ebugging

+e"gging is not Testing!

+e"gging always occrs as aconse*ence of testing!

+e"gging attempts to $nd the case ofan error and correct it!


8/27

Wen to "tart Testing in

"'()Phases of S+&

'easi"ility Stdy

-e*irements Analysis and Speci$cation+esign

&oding

Testing.aintenance


9/27

Types Of Testing

White Box Testing Blac(Box Testing

System Testing

/sa"ility Testing

Static Testing +ynamic TestingPerformance Test

Wal(throgh /nit Testing

&ode -e#iews Integration Testing


10/27

Wite Bo* Testing

The internals of software are tested to ma(e sre thatthey operate according to speci$cation and design!

Test cases are "ased on internal strctre of software!

+reas

&ode &o#erage ,Statement &o#erage, Branch&o#erage, &ondition &o#erage ,oop &o#erage, Path&o#erage ,+ata 'low &o#erage!

Tecniueso 'low graph testing ,0raph matrices ,&ontrol strctre

testing , +ata 1ow testing!


11/27

"tatic Testing

Static testing of a program carried ot withot

execting the program!

It aims to $nd defects in the software prodct in the

early stages of software de#elopment, so that they can"e $xed easily!

It can $nd errors that occr on paths nco#ered "ytesting

It explores all possi"le exection paths in a program atcompile time!

Wo

o By a team of indi#idals!

o By indi#idal who didn2t write the code!


12/27

)ode -evie#

o A code re#iew can "e done as a special (ind ofinspection in which the team examines a sample ofcode and $xes any defects in it! In a code re#iew, a

defect is a "loc( of code which does not properlyimplement its re*irements, which does not fnction asthe programmer intended!

o Are the #aria"les name meaningfl?

o Are the #aria"les initialied?

o Are pointers initialied properly?

o Are there in$nite loops?

o 4as the sage of operators li(e 5 and 55 or 6 and 66"een chec(ed or not?


13/27

)ode Inspection

It is the most formal techni*e!

The aim of this re#iew type is to nco#er

defects in the docment in the early stages ofsoftware de#elopment and there"y impro#ethe *ality of the prodct!

An inspection is one of the most common

re#iew practices fond in software pro7ects! Inan inspection, a wor( prodct is selected forre#iew and a team is gathered for aninspection meeting to re#iew the wor(

prodct!


14/27

)odeInspection.continued/0

The stages in the inspections process are:

1lanning:The inspection is planned "y the moderator!

Overvie# meeting:The athor descri"es the "ac(grond of the wor(prodct!

1reparation:8ach inspector examines the wor( prodct to identify possi"le

defects! Inspection meeting: +ring this meeting the reader reads throgh the wor(

prodct, part "y part and the inspectors point ot the defects for e#ery part!

-e#or2:The athor ma(es changes to the wor( prodct according to theaction plans from the inspection meeting!

Follo#up:The changes "y the athor are chec(ed to ma(e sre e#erything iscorrect!

The process is ended "y the moderator when it satis$es some prede$ned exit

criteria!


15/27

3nit Testing

Objectives

The primary goal of nit testing is to ta(e thesmallest modle of testa"le software, and rnning itin isolation "y sing prepared test cases and

comparing with the actal reslt to test the interfaces"etween modles!

Wen

After modles are coded

Wo +e#eloper9programmer

4etods

oWhite Box testing techni*es


16/27

Wat are "tubs, 'rivers !

A st" is a compter program which is sedas a s"stitte for the "ody of a softwaremodle or a dmmy modle which simlates

the fnction of a modle called "y a gi#enmodle nder test!

+ri#er a modle which transmits test cases inthe form of inpt argments to the gi#enmodle nder test and either prints orinterprets the reslts prodced "y it!


17/27

Integration Testing

Objectives To technically #erify proper interfacing

"etween modles, and within s"%systemsthat satisfy fnctional re*irement!

Wen

After modles are nit tested

Wo

+e#elopers9Programmer4etods

o White Box techni*es

o Blac( Box techni*es


18/27

Types Of Integration Testing

Top-Down Integration testing

Bottom-Up Integration testing

T ' I i


19/27

Top 'o#n IntegrationTesting

A

B

St"

St"

St"

A

B

&

St"

St"

st"

St"

Bottom 3p Integration


20/27

Bottom 3p Integrationtesting

Test+ri#ers

e#el

e#el %; e#el %;

e#el e#el

Test+ri#ersTest+ri#ers

Test+ri#ers

Test+ri#ers


21/27

-egression Testing

Objectives

o It is sed to chec(s falts, defects propagatedto other modles "y changes made to

existing program!oThis testing is sed to redce the side e)ects

of changes!

oTesting is done "y re%execting the pre#ios

#ersions of the application!

WoProgrammers or independent testers


22/27

Blac2 Bo* Testing

In the "lac(%"ox testing approach, test casesare designed sing only the fnctionalspeci$cation of the software, i!e! withot any(nowledge of the internal strctre of thesoftware!

It explains the process of gi#ing the inpt tothe system and chec(ing the otpt, withotconsidering how the system generates theotpt! It is also (nown as Beha#ioral Testing!

It attempts to $nd error in the external

"eha#ior of the code!


23/27

"ystem TestingObjectives

The goal of system testing is not to $nd ot falts "t todemonstrate performance!

Wat

The system testing is actally a series of di)erent tests ,

primary prpose of which is to flly exercise the system!

All wor( to #erify that all system elements ha#e "eenproperly integrated and perform allocated fnctions!

Wen

After Integration TestingWo

+e#elopment Team


24/27

+cceptance Testing

Objectives

To #erify that the system meets the ser re*irements!

It is the system testing performed "y the cstomer

him9herself after the prodct deli#ery to determinewhether to accept or re7ect the deli#ered prodct!

Wen

After System Testing

Wo/sers 9 8nd /sers

4etods

o Blac( Box techni*es


25/27

+lpa Testing

It is a testing in which the #ersion of completesoftware is tested "y the cstomer nder thesper#ision of de#eloper!

This testing is performed at the de#eloper


26/27

Beta Testing

It is a testing in which software is tested "y acstomer withot the de#eloper "eingpresent!

This testing is performing at the cstomer


27/27

Tan2 5ou

Date post:	24-Feb-2018
Category:	Documents
Upload:	kishorenaga
View:	219 times
Download:	0 times

typesoftesting-130623074510-phpapp01

Documents