Market Aligned Skills Training (MAST) – Software Testing Training Module

The Market Aligned Skills Training (MAST) – Software Testing Training Module is designed to equip underprivileged youth with essential software testing skills, preparing them for employment in the IT industry. Developed by the American India Foundation in collaboration with Mumbai University’s Garware Institute of Career Education and Development, this module provides a structured approach to software testing.

1. AIF) 2.

2. SOFTWARE TESTING
TRAINING MODULE

3. ‘About the American India Foundation

‘The American india Foundation i coments to catan sdal and economic hang nn, abu à
last beg Between he Unte Ste nd ia tough igh impact imevetions messen, tion,
Pub heath, and eaership development. Working closely wi cakommuntes, AF partners with NGOS to
help and test inovatwe sons and withgoverment to erste apd scale sstamale impact Found in
200 tthe inate of resident Canton folowing suggestion from Indian Prime Minster apoyo, A has
impacted the es of 4 min of nd’ poo

Learn or at wine Along
‘About the Market Aligned Sills Training (MAST) program

Market Aligned Sis Traing (MAST provides unemployed young people with a comprehensive salsa
‘hat equips them wth he knowledge and il needed secure employment and css on heb, MAST not
onbmeets the growing demands ofthe desing local Industries across the county thameses nas youth
population become por engines ofthe economy

AUF Team: Hanuman Raat, ami Aja Romea Kay Mascarenhas

‘American India Foundation

108 oo, UF Cy Court MG Road,
Near Standerpur Mer Staton, Gurgaon 122002

2366. 45h tree, lor New York, WY 20017,

‘is documents creoed forthe we of undrrlge ou under Aeron da Foundation Maret Aligned
iis Waning AST Program.

4. ACKNOWLEDGEMENTS

‘Tis ulm has ben developed by American nla Foundation Tustin partnership wth Mumbai Univers
anwar Instue of Carer Education and Development (ICED) as par of ts Market Algned Ss Tang
(HAST) Program The supported by Franklin Templeton nda s part of he program.

‘This crrclum i designed spec keeping in mind the ein needs of youth having poorte average
cductonal background. Te ojete of Is curcuum sto equip APs MAST caaidates wi essen of
Share testa prints, td, stem, Opa, procs of exc stare program er aplico
‘ith the intent offing he sofware Bs

We re gael o Ms shor! Ter rom Mumba Univers Garware astute of Career Education and
evelopment (IED) for helping usin developing the content We are lso thankful 1 Dr Mea Tall,
Director ICED and Ms. Spa Briar, Asstant rector ICED forthe continuous suport and gudance in
developing tis cual

We a ao tario to Mr Hanumant Rawat Senior Advisor AIF and Mr amie As, rogram Manager AF to
tude te conten developmen and design tam regul

8. SOFTWARE IE

Software is a sto instructions executed by a computer which ae designed to pe Horm a particu task
General these st of Instructns are termed as programs These ae of two types

1. plain Sata
2. System Software

Application Software:

‘These are to called end ser programe such a
+ Pinto Paycheds
+ Play Moral Komo
+ Keep Teak OY Stamp Cotecton
+ DourTaes
+ Generate Fancy Newser
+ cuide Robots
+ Keep Budge
+ Draw A Rowchart
+ Design Acar
‘The amples of Appleton Sofware ae: MS excel, word procesingSftare Ike MS word, werdpsd and
sata soute le MS access, rado ete

System Softwar

Phelps computer carryout sas task Examples ae
+ Operating Stems such as Master Control Programs, BOS (Bas Input Output te and Some Uses
‘Which are Bano OS
+ Transtors such as Program Language Transtors/Complers
The Examples of Applicaton Software are: Windows Linux and Mac te

SOFTWARE TESTING DS

Software testing a proces of executing a program or application with the tert offing the software bus
ean lo be sated as the proces of abating and venting that a sofware program or pci o product
‘ees the business and tchat requirements that pudes design and depen.
In other words, Software testing san investigation conducted to provide stakeholders wit formation about
the au ofthe produc or Service under ts Software esting cn abo provide an objective Independent
vie of he stare tao the business to apprecte and understand the risks of ste implementation.
Test techniques ince the process of executing a program or application wth the itent of Aning sofware
bogs torso other defect), and very thatthe Sfar products or use.
Software tes votes the extuon of aware component or stem component to evaluate one or more
properties of interest In general, these properties indice the extent to whch the component or stem s
der test. Therefore

the proces exec program with he intention of ding eros
+ Ian shout presence of bugs br never the absence
+ Agoodtescas one that has high probably of detecting an uncovered defect not ene hat shows

thatthe rogamos carey

y

Sofware Testing Ting Module |

9. COLE +

+ iis imposible to ts your own program.
+ asthe numberof detected defects na piece o software increases, the probability ofthe existence of more
Undetcted defecto nremer

The Need of Software Testing?

Sofware tstngis very Important because ofthe folowing reason
Y. Sofware tenting reed to point out the defects and Gros tht were made dung the

software development poses.
2.1 essential ino I mas sor ofthe customers relabl and tele satisfaction In the software
2pleaton,

3. has to ensure the quay ofthe produc. Quality product else tothe customers helps in ring
the conidence (Kram moro about Sofware Ql)

4 Testing necessary noter to provide the facie to th customer he the der of high quay
Product or software sppiaton which require ler maintenance cost and ence re ino more
curt, consiste and ret resus.

5, Tstngisrequrefr an fective performance sofware pplaon or product

6s Important t ensure that the appt shoul not rest nt any ales because an e very
‘pensive nthe ature rin the ter tages te development

17 required tome ny sofware busines sustnaie,

8. Software Teng ie necessary because we ll male mistakes. Some of those makes re unimportant, ut
some of them are expensive o dangerous We neato check ever and anything we produce because
‘things can abeys go wrong humans make mises lth me.

SOFTWAR!
TESTING
sa

tort

LS A

Sofware esting Training Module

10. ar

Goals and Objective of Software Testing
Software tesing haps in fiating the oftware pplication o product gat business nd user requirements
Its very important to hae good ts coverage m order o ts the software appliatoncomgletely and make
Insure that t's performing wel and as per the pelicans. The goalsand ojete software esting ae:

+ ding defects which may might ave cested by the programmer whl developing the software,

+ Ganingconiácncein and providing formation about he eve af qual

+ o mature thatthe en result meets the business nd user requirements

+ To ensure that it sass the Business Requirement Speciation (DS) and System Requtement

Specteaions (585.

+ Tominthecondeceof the ustmers by proving them a ua product
Softare testing makes sure thatthe testing is bin dane property and Nene the stem is ray or use.
Good coverage means tat the testing hasbeen done 1o cover he various artos he frctonaty of the
pletion compat ofthe aplcaton wih the 05, hardware and ferent yes of browser, performance
es totes the performance of the aplcaon and cad ten to mae sure thatthe tern veal and
‘houldnot or ere hou ot be any locking ues. determine hat the appli cn be lo
‘easy othe machine and whut ay resistance. Hence the application en enn and se

SOFTWARE BUGS

A software bug i fale or fow in a progam that produces undesired o incorrect resulta err that
prevents the apa from fuctis Renaud Most common enon or sofware bu human mites
Insoftware deren and coding

Important Reasons for Software Bugs
+ Sofware complet
+ Conde equements
+ Poor documented code
+ Sofware development 0
+ cotas tester
1. Msconmunation ria Comunicar: Undesrequtements and mnterretan requirements
are to major actos cating defects n sofware
2. Sofware Complex: The comply af cren software aptations an be fut 10 comorehend
for anyone without experience ln modern dn fare development. Wand pe Iterace, lee
‘ever and tbe apple, a communion enormous rana data, andere
aps have all contibted to he eponentl growth in sofware/ytem compe
|
Sofware Tsing Tang Moda

11. MODULE:

2. Programming Eros: experiences programmers orpragrammers without proper domain none can
invedce simple mistakes while coding

4 Changing Requirements: The customer may not understand the elects of changes or may understand
and request hem anya = redes, eeheduling o engines, eet o ether projets, work ead
Completed that may Rave tobe redone or town ut, hardware eqarement that maybe ate,

5 Tm Pressures: When deadinesloom andthe crunch comes, mistake wilbe made.

6. Poorly Documented Code t's tough to maintain and modify code that i badly wraten or poor

sore bug

thai own bugs rare pool documented resulting in aed bugs
8 Obsolete Automation Seis ; Weng automation srt takes lot of Hime especialy fr complex

9. Lackof Sled Tester: Hina sl testers wth domain knowledge extremely important for sucess
ofan projet, Bu oppeintngal experienced test's ot possible lr al companies. Domain nome
Sa the tester’ ay o ind detects cn produc igh quality software, Compromise on ay of hs can
Festin buy sohuare

Software Testing Process
+ Planing and cont
+ Analysis and Design
+ Implementation nd Execution
+ lating tera a Reporting
+ Test Gore setts

e

1, Planning and Control
Tes planning as following major asis

To determine the scope and risks anden the ajetes ef testing
Yo determine the ts approach.

To implement he test pal andr the ts strategy

To the requires tes resources he peopl, st entnments Cs, et.
Toschedule est anal and design sks, test implementation, econ and evaluation
To determine the Ea criteria we neto et tera suchas Coverage rte,

Test contol ae the folowing major ais:

Tomessure and ana the results of eviews and testing
To mentor and documen progress, es coverage and et errs
To provide information on testing

To mate decions

o!

Sofware Testing Training Module

12. ar

2. Analysis and Design:
Test anal nd Tet Designs the following major tasks
+ Toldentiy ts conditions
+ Todesgnthetets
+ To salute estab ofthe requirements and sistem
+ To designe test emironment stp and ide nd required naswuctur and tos
3: Implementation and Execution:
During st implementation nd seco, we tte the test coos into test cases and procedures and
ter testwar such asserts for automaton the tes enuionment and any other ts infrastructure
4 Test implementation
Test implementation hs he folowing major ask
del and peris our tes css y using techniques andereat test ata for hose tests.
+ Toceatetest ses rom the tet cts for ecient ts exciton,
+ Toimpement and very the endronment
Test execution as te folowing major ak
+ Toexeut tes suites and inal est cases following he est procedures

+ Tore-emete the tess that previous fled in order to conf fc Ths known as conemation
testing rretestag

+ Tologthe outcome ofthe test eseuon andrecor he denies and vesons othe sftuareunder
test. test og sun forthe au ti

+ Tecompareacal results with expected results

+ To report dsceponcs as Inert where tete are ferences between actual and expected

Fvaluating Bt criteria nd Reporting
Bt ter comesito pure when
‘+ Maxum test ses are executed with cen pss prcetage
+ Bug tefl low certain ve
+ Whenachievene deines
lating estee has the following majo ts
+ Tocheck the test gs gast he et eter speed ints panning
+ To es more test ar needed orf the it ceria pei shoud be changed
+ Tourte aes summary report fr stalaholes
6. Test Closure activities

Test sure actitesare one when sofware sdebered The testing can be lose for theater easons

‘+ Whenallthe formation hasbeen tre which are ed the testing
+ Wena project scanceled
+ whensome tags che
+ Wena maintenance release o updates done.

Test done acti ave the folowing asi:

1 To heck which planed elles are actualy delivered and to ensure tat al niet pets
have Beenrezhed

+ Toate and archive estar such a ep ts emkonments, et forte reuse
+ Tohandovethe testware tothe maintenance organization. They il ve support tothe software
Toute how the esting went aná leen eso for futur releases and projets

of
Solar Tsing Tang Moda

13. COLE +

Test Initiation Criteria

Ting: Assoon as wo have a sofware requirement
Objective: Totraprequrement rated lots as ery soy can Belden
Approach estregurenens
We prevent incorct requrements rom being incorporated the design and implementation where they
willbe more cut and expensive 1 And and correc. Yo passthrough the quality gateway and be included
Inthe requiera speciation, a equerent must poss a number of tess. These tests ae concerned wth
(su that the requirements are ara, and do not causes ron y Being unsuñabl for eign and
Implementation stage aer inthe projet

Testing Services

Test completion Criteria
Timing: Assoon as we have a software requirements
Objective: To raprequiements rated defects as early soy can be ento
Approach: Testregurements

Participants in Testing
Timing: Assoon a we have à software requirements
Objective: To raprequiementreated detects as ery as they canbe idee
Approach: Testroqurements

Best practices of Testing
+ eat ana your test rests org
+ Learmtomasinze the test coverage
+ To ensure maximum test cv beak your appeation under test (AUT) Into smaller funciona
modes
+ Write your tet ses requirement anand design phase sl
2 Make your est eases aaa to developers rie o cong
+ possible ide and group your est ases for regresión esting
+ Programmer should ot test ther wn code
+ Go beyond requirement esting

Do ot ignore the tet est estes wie respected they not ony lg the bus But lo provide solos.
‘Though 100 percent ts coverage might ot be possible sl you can always te o reach ea To ensure
Tan test coverage break your applkalo unde et (AUT to anale funcional modules. We tet
(ses on such Individual nt modes. As I posse break these modules into smaler pas. ie writing
test cases, wt est cases fr intended fanctonalty Ast Le ova coi according to requirements.

14. ar

under tes We you st aes In equremet anal and desig phase ise This way you can ensure ll
the requirements re testable, Make your text cies alle to developers pro to coding. Do ep yout
Lette with you wating to et ral pl reise for testing. thinking tat you can og more bugs et
developers anaye your test es thorough 0 develop quay apple ation This wif a sae tee worm
posible dently and group your testcase fr region testing Tis wil ensure quick and efecto manual
regression esting Programmes should no et ther own code As cussed in our previous pot as unt
testigo! developed applcaton should be enough or developers t reas he aplcatin tr testers ut You
(testes) shold not force developers to release the product o testi, Let them take the own ne. Everyone
from lea to manger know when the moe /opat released or esting ad hey can estimate the testing
tise accordingly This sa tpl tato nape projet environment

Challenges in Testing

+ Complete testing simposio

+ Testers miete resources because he ol fr the company's proces ths

+ Testgroups operate under motile mins, often config, ore arts

+ Test groups often ack sd programmers, and a vision of appropiate projets that would keep
Complete testing impossible. Ter ino simple anse or this. Therefore eter ve aná bene trade.
Testers maleate resources because they fal forthe company process myths. Testers have 1 ely on thet
wits, nat on someone ess compliance wth a (legs bu vel) proces. Ts groups operate under
mutige mins, often cof, rey artclte. We ic ur et to conformo ou testing mision. Tet
Aou often kil propammers and vino! appropriate projets hat would keep programming estes
chotenges

Test Methods

Static vs. Dynamic Testing

State. name testing: tate testing i olen inl, a rocfreading ls when programming tet
‘stor check source coe structure or comple (precomplers) check stax and daa lou 3 sai program
rls Dynami testing aes lace when the program ses run

4
Solar Tsing Tang Moda

15. COLE +

The Box Approach
+ White boxes
+ Blackbox testing
+ aan
+ Grey bactesting

White-Box Testing:

White bae testing ao known as car box testing, las ox testing, bansparent box testing and structural
testing y seeing the source Code) tests Internal strates or workings 8 program, 3 opposed to the
foneionaty exposed tothe enduses In white box testng an ternal perspective of he system, s well a5
programing sil, ae used to design test ass

White box esting

he

Black Box Testing

Bah bor testing weats e software a “ch bo examiing unconaty without any knowledge o ntrmal
implementar, without sing the sure code The testers are oly ae of what he Sofware supposed
todo, not how toes

Visual Testing

‘The aim of vial testing to roid devlapes withthe by to examine whit mas happening atthe po of
Software by presenting te data such a may thatthe developer onesie the formation she he
reqs, and he ntermaton i exprese cat

Grey Box Testing

rey box testing [American selig: gay ba esting) involves having nome of internal dt structures and
grita for purposes of desing tests, while exec tose ets a the se o ad box eu. The tester
isnt required to have ul acess tothe software source code, Maniulatiginpa data and formating output
dont quays greybox because he put and output are dry outside ote "lack box that we are cata
nen under rt

+ Decision table testa.
+ pos testing

+ Equnalence partion
+ Soundaryvae nas
> cueca

+ ior guessing

Sofware esting Training Module

16. ar

+ Site arson testo
+ Use case testing
+ Wserstor testing
+ Domain analy
+ Combining tecmiave

Decision Table Based Testing

‘This approach the most rigorous one and dal Implemented when the number of combinations of
con en under varying condos.

Equivalence Class Partitioning:

This technique use to reduce the number of possible Inputs o mal yet fective Input. Used 1 est
an appcatonexhustely and vod tedundany of inputs 15 done by ding Inputs into cases and
tna valve om ee cs

Boundary Value Analysis
‘The most commonly use back bs testing techriave, Boundary Value Anais or BVA fed td the
‘erin the boundaries of op values rather than the center.

Cause ffect Graphing Technique

‘The technique considers a sent der eternal behavior ony a in sein test case which
ret Causes tects terete estas nthe loremertioed statement, Cause mpls ant input
Condition ic result in mea change a sytem whe ec mp a output consi bought by
‘combination of eave.

Error Guessing:

‘The suceso technique sly dependent onthe experiance ofthe tester There ar no tots and
techniques such, bu one an wrt test cases eier he reading the document or uhle ennuntering,
shundocumented err during the testing

Black Box Test Advantages
+ cient when usedon ge em

Testingis balanced and uptejudced, ince he ester and developer re independent o eachother

Tester an be nontechnical

eta funciona nome str forthe testers ot necessary

Tess ate done oman end users pino ie because the end use should accept the stem. This

testing technique sometimes abo called Aceptnce tes)

Testing help to dentyvaguenest and contradiction in functionalspeficatons

Test cases canbe designed as soon a the funcional pecas are complete

j
Sofwar Ting Vaig Moda 1

17. COLE +

Black Box Test Disadvantages,
+ ess anbe redundant fared run bythe sftare designer
+ Tes cases ar eremely filo be designed wthout car and concise specications

+ Testing of ever possible input stream i not possible because A time-consuming and this would
seul leave many program paths untested

+ ets pb overestimated at es
+ Cont be used fr testing complex segments of code

White bo testing ao known a structural esta or code ases test. sa methodology whic ensures
nd ats sofware apple mechanism, nern framework and objects and companies

This method of testing not only verifies code as pr the design specications, but aio uncovers an
appteaon'svlneabites

Pts ao known as wansparat bn, glass bx, and clear box esting st cea visuals the softwares
Internal mechanisms fora software engineering team

During the white box test phase, a cade run wth preselected input ale to vale the presets
output values. a mimach fund, e imples tat the software applcanen s marred by a bug Ts
roces als meus ring software cde stubs and ers

‘The mostmortant par inthe white box testing meth the code coverage anal which empowersa
software engineering ten find the aren acide whichis unesected y genset ts case er
engin improving 3 software apar quali There are fret techniques which an be ue
perform the code coverage als Some of these ae

Statement Coverage: Ts technique is used tts every possble statement at east once, Cantata the
preferedtool when sing ths technique.
‘ection Coverage This inches test evry posse decision condon and other condkionl ops at

least once. TEATPATH, support €, Cr, and Java applications, 1 he goto too when is tchniaue I
fotones.

Condon Coverage: Ths mates one tne code excuton mandatory then the condtions ae tested

Decsion/Contion Coverage: This is a mie technique wich implemented to es al the Decision /
Condition coverage at ast once while the code execute
Mulsple Condition Coverage: a hs typeof white box testing technique, ech entry point o stem has

White Box Test Advantages

+ Code optimizacion by revealing hidden errors

+ Transparency ofthe internal coding structure which shlpfulin dering the type input atanceded
totestan aplication tay

+ Covers al possible pas ol à code thereby, empoweig a software engineering team to conduct
‘torough aplican testing

+ Enables poyrammetoinvospctbecausedeveaperscancaeluly desoibeanynewinplementaon

+ Tes cases canbe ey automated

+ ies ergineeing base rules t stop testing an apkaton.

9

Sofware Testing Training Module

18. ar

White Box Test Disadvantages

+ A comple and expensive procedure which require the adrotness of a seasoned profesional,
‘pert In programming and understanding of neal structure of code

+ Updated test srt require when the implementation changing to ten

+ East testing becomes ven more complexusin th wit bos esting method ithe application
‘oltre size

+ Some conditions mp be untested ats nt reali ts very sige one

+ Necessity to create fl ange o inputs to test each path and codi make he white box testing
method me contuming

+ Delecsinthe code may ot be detected or may beintroduced considering he ground ofan
‘ach ne by ine path by pth

Performedat Levels Whe oxTestingis appableto__ Tis method of testing is may
lower hs Unit and Integration apple tohigher evt oferto
par ihe acceptance and ste

Performed oy Sofware Developers Independent Sofware esters

Programming Knowledge Profesional peroming he method No such tea necessary when
torest the functional ofan Comes to black boxes
Sppkaton should be tnowledgesble

estic program lares

sis of Test Case Design Dealed eg documentsare — Requrementspecifatins documents
sent design te cases when are enough to dentes cases fr
testaganappeaton ui th white black ox test

boxtesng method

Focus of Testing ‘te box testing focus on how the Thi typeof eg uses on what
pus ar care out an he code of being are ut andthe functoalty
ate oran

Lolo compo eme Moser

of
Sofware Testing Ting Module |

19. COLE +

En

Stati Testing i type of testing in which the code not executed canbe done manual or by a Set
cof tools Ths ype af testing chcks the cod, requirement documents and design document and pts
ets comments onthe work document When the software no personal andinscto, we perm
cut testing to analyse the software non tune enironment With state test, we ty 0 And
fut the eros cade fas ad potently maldus cde inthe satwareappeation It stat ale in
evelopment fe yl an hence a0 called verison testing tate testing can be done on Work
documents requremen speceaons, design documents, source ode, Wt las, ts ps andes
ases, web page content. indes
+ Inspection: Mere the mainpurpot to ind ects Code wakthroughsre conducted moderate.
Isa foal ype of review where checkt is prepared to reve the werk documents
Waltvouph: is type oftechique a meeting ea by author to ul the product. Partcants
an questions anda seri asigne to make notes
‘+ Technical reviews In ths ype of sat esting technical round of review conducted to check if
the ode made acord to technical spectations and standard. General the test plas, test
strategy and test serps ar reviewed hee
+ Informal eviews: Sta estngtechigue in ich he document eiewedinformaly anima
comments ate provide.

ME static testing tecnniques

‘yam testing à done when the code sn operation mode. Dyname testing is performed in runtime
enonment When the code beng executed input with value, the esto he output of he code
[sche and compared with the expected output. With this we can observe the functional Behavior
ofthe software, monter the system memory, CPU response time, perfomance ofthe ste. Dam.
est also trown a valdaton testing evaluating the fished product. Dmami testing of 0 types
Fanctorl Testo and Non functional en

+ Unit Testing: Testing of nial modules by developers The source code stes ni

+ Integration Teting Testing te neface between diferent modules then they ae joined

+ system Testing: Testing performed onthe tem a whole

+ acceptance Testing: Testing done rm user pain of ew at ser en

Sofware esting Training Module

20. MODULE»

THE DIFFERENCE BETWEEN STATIC & DYNAMIC TEST TECHNIQUES

1 State Tes wie Boxtestng ah done 1. Dynami Testing onthe oer hands done at
teal Stage development feces ‘the ater stage of evelopment ck,
(More os elec han rame eng

2: Sacos has more statement coverage 2: Dynamic Testing has less statement stage
an ame testing shorter ene because covers ited area of ode

3: done before code deployment Tis done afer code deployment

“ts perormedin Veran tage Tee done nvalanton Sage

5: This typeof testing done without the

This typeof erection done withthe

execution of code, recto of code
Sac es gs assesment of code aswell 5. Ojai Testing pes batleneck ofthe
se documentation, sofware system,
7 Insane Test techniques sche 7, m DimamiTosng technaus te ts caves are
repre for testing process svete,
8: Sate Testing Methods nido Waltvougs, 5, Oyamietesting volves functional and

code ec onto testing

Fundamentals of Software Quality
+ Quai
+ Quai ews
+ Quai and Productivity
+ Employeimevementin Quatty

Quality:

+ Mis oe station alles fte tact comp Tom Meca

+ Qualys another name of content meting customers requirements, cost der schedule and
sees fered

y
Sofware Testing Ting Module |

21. COLE +

2 Quai must be mesurable and shui prete
+ Quai must be wel definan shouldbe Quant
+ Qualny objectives shold be achievable andtraceable

Quality Views:
À Customers View
+ Deering the ge product
+ Satshing customers needs
+ Mesingthe customer expectations
+ Trent every customer with Integrity courte respect
Since Qualys peeved value by the customers, ther ew ret the following factors
1. Delering the right product
The product hich eee, shouldbe the ane ares customer requirements. The produc should
ont athe features enone in requirement pecieatons
2, sas customer need

The product maybe satisfying a requirements but may sil fil shor of his needs The Ananda panning
system may have al the features for creating a financial pan and perform ars, ut i the ana
‘ports do ot provide the customer ay larg then my no be stg hs eed

3: Meeting customer expectations

Customer expectation may tite wo categories Vi, xpresed expectation documented inrequement
‘Speciation nd imgledexpectanons which may nat form a parol requrement specheabons

1. Suppliers View
+ ong the rit thing
+ Doigithe ret way
+ Doit the fst tine
+ Doing itin tne

Quality Means:

Consistently meeting customer needs inten of
+ Requirements
+ Devery schedule
+ Service

Ius ne process of meeting the customer requirements est time and very tne, which ft for use to perform
Es ended unten, wi resonable cost and wth me

Software Quality:
Site Ts:

+ Aimatastomer dela

+ ve mesurable ects

+ Understand requirements acuratey have a tough aceablty AL requirements

+ implement the pad check ce inc phase

+ Det and remove defects eat as posite: presents bete han cure

+ Site change onl and veron contol must ext

+ Follow es tus tandréomentns for amie, commenting. con and documentation

+ Start compli and alla simple meri

E
far Ting Taming Module

24. 100062

SOFTWARE VERIFICATION AND VALIDATION MI
+ vento
+ vato

Objectives:
+ To Understand escaneo festin anal
+ To ie iat techniques of vefcatn aná validation
+ 10 Bphinthe guidelines associated various techniques
+ 1 BphintheV model

Verification
+ its sisas approach to evaluate whether a software product fu the requirements or conditions
Imposed on ther
+ iis abo called state teste
+ Is done by stematalh reading the contents of à sofware product wäh the intention of detecting
des
+ helps inidenting not ny presence of ects but io their cation
‘Afters app a ara points during the SOL o pui he produc as progress through vais
+ Temas ore that the products designed to ever al fnetonaty o the customer
+ Is done atthe starting o the development process 1 includes reviews and meets, wlkthrughs,
Inspection ett elute document, as, code requirements and speciation.
Suppe you are bling table Here the veia bout checking he parts ofthe tab wheter al the
four legs ae cre ze o ot one lg o able nat ofthe ight sie wl blanc the end pre.
Si har sao note in case te Stare product pat Hany ature of soar productor
2ppkatonsnetup tothe mark Fan detect found hen wl res vo tale of he end prod Hence,
ration very importar aes place atthe ato developmen proces

Advantages of Software Verification

rien his m owerng down the count ofthe defect in the ter sages of development

+ ring the product athe starting phase of the development wl pin understanding the product n
bee way.

+ reduce the chances of lues the software application product,

4
Solar Tsing Tang Moda 1

25. MODULEZ

Walkthrough

+ Aninormal proces, tated bythe author of sofware product colleague or sane inc
detects and fr suggesting improvements

+ normal

ot planned

+ Author pls the product obseratons
+ Collage comes out with observations

+ Author

rides cation ru

+ Author hate down relevant pois and aks correct actions
During he walkthrough meeting the presenter ntrodues the material to al the partiganen order o mate
‘hema wih Een wen the walkvoughscan ein din potential bus, they areusedorimowiedge
ati orconmuniaion purpose

Fer amp

in programmer who as ten the code il fm present he cadefucon by fection rin

byline. The reer then question he progama for any doubs queries

Inspection

‘thorough, word op wrdcheching o sofware producto part of produc) wth the intention of:
+ Loasthgdetects
+ Confeming traceabity o elsa requirements
+ checking for conformance to relevant standards and comentons

typical inspection session tates around 90-120 minutes and type they detect 30.70% of ole design and
cod errors The bete l he inspection sto And errors in the program, ths improving the quality of the

wor

Preconditions for inspection

The proces oi

+ System overview presertedt specton

+ Codes

seceaton must be walle

Team members mus be fara with te organisation standard
Syetactaly conc code mest be avaiable
An rocks sould be prepared

inspections

soit document are dtrbuted to npecton team in chance

+ Inspection tke place and acer ror ae noted
+ Modtcaon re made torepakedicoveredenors

+ Respect
Ines Mar

on mayor may ete required
Roe

+ Moderator

+ Reader
+ Recorder

Author

‘an authors the person who oil constructed the work product. The author il adress specie questions
‘hat arise concening the content of the work product, The author willbe timate responsible for updating the
‘work productater the npectone ga programmer

Sofware Ting Taming Module

26. 100062

Moderator
‘The moderator response or ensuring thatthe discusion proceed on the productive ines and thatthe
parscpans focus ther tention on funding error.

Reader

hereadristsponsi or documenting a eects that are rom he inspection meeting. This documentation
lind where the defect was found

Inspector

‘lof he inspection Team ddl a aso considered play he inspector le, independent e other roles
sed. The Inspector roles response or anlying and detecting defects within the work product

Example -Inspection checklist

Control Flow
+ WI esoo? termine
+ DOJEND statements match

Data Declaration

+ ell aril dere
+ rearaysand stings nal property

Calculation
+ Non ithe varier

Input/Output
+ Fes opened before ue and led ater vse
+ Are 70 tors handled

Case Study Inspection:
Regurement
Me program shall convert centrado vale to Fahrenheit and vice versa starting rom 010. 300 with
Interna 20
+ The program halgit al entrado and Fahrenheit valves

‘The above seated the requrement for developing program tbe developed Clanguage.Thisrequrement
willbe the input or developing to generate appropriate code

Review
+ Follow up: subsequent eamination ofa product forthe purpose o monitoring arar charges
+ Formal or oficia examination

‘+ Aprocessin which one o more persons ches changed documents or data to determine the changes

|
Sofware Testing Taie Module |

27. COLE +

+ nanas undrtata at fu paint in me to determine the degree to which stated objects hve
been reached. This general sed a as o decision making. nung updating plas

Verication

Validation
+ Iris in approach o evaluate whether he Anal, a uit sofware product ul is specie
intended we.
+ tesa caledas dynamic testing
+ tts done systemataly bythe presence of def rt ther location

+ Risnecesanyte demorstrat not jt that he sofware ining what supposedto do, ut 0 ot
Aoingwhat tis at supposed todo

‘+ Method: esting each software produc at each phase o cyl sing est lan. ts cases

+ Voldaton noting but proces ol fring ut ifthe product Being ult ght?

+ Te software product shuld faneinaly do what i supposed o, shoul satya the function
requirements et by e customer/user

Valen is done during or at te end ofthe development pocesin oder to determine.

Whether th product satis specified requirements Vallon sl performed by dynamic testing,

testing wtheseutenon a computer

+ Vado andvenfcaton process hand hand, but iy vida process rt afro
proces ends

+ sltypes testing methods at basally cated ut during te validation proces. Test plan test us and
testcase are drop, which are used rng he various pass of valia process.

1 Te phases ised in vation proces are: Code wallon Code testing, iteration van
integration test. anesonlatdasontencsoal testing and stem Ju acceptance test validation

Validation - Levels of Testing
+ Unt tse
+ Integration testing
+ Spsem tern,
+ User acceptance testing
Vitis males pice of software hat can be testen lan. Testing of uch vit ale unites

‘Thetestng conducted to check whether modes wrk proper when integrated sinegaton testing. Generally
ie fantom testing

System testing s testing done in order check whether the system works proper as whole na simulated test

q
8 ———

28. 100062

Acceptance testing ia testing conducted by customer in order to very hat system works proper in his
‘naronmentand hi needs ae ated

Unit Testing

‘+ Aunts the smates testable part of an aplican Ik functions, dases, procedures, interfaces. Unit
testing method by which individual uns of sourcecode are tested to etes thoy are for se
design andrequrements and behaves 3 espect,

+ Te goal of ut testing so segegte each prt ol he program and test thatthe india parts ae
oran correct

‘+ Tis means tat for any function or procedure when a st of inputs ro shen then shoul reto he
proper valves shuld hand the fares race during the cause of exciton when any mal
Inputs gen

+ Aun test provides a write contrat thatthe pec of code must asu. Henceit as several benefits
+ Unt testing Is basica done before integration

‘Method Used for unit testing: White Box Testing method used for executing the un test.

‘When Unt esting shoul be done? Unit testing shoud be done before Integration testing

y hom nt testing should be done? Uni esting shou be done by the developers.

Unit Testing

‘Advantages of Unit Testing
Issues are founda ea stage. Since uit testing are cared ou by developers where he test hi nda
(ode before the integration. Hence the ses can be found very ea aná an be resolved then and there
hou Impacng the other pee of odes.

Unit testng hip in malntaning and changing the coe. Thi pol by making the code interdependent
so atun testing can be eaeuted. Hence tances of impact of changes 1 any the code gts reduce

Ilo hop in reducing the cost o bug es, since the bug are found ea in un esti ence, st imagine the
coste bug cura ding tete stapes f development in dung stem esting o ig acceptance tse.

+ Unt estr helps in smplfying the debugin process. suppose à tes fl then ony atest changes
‘aden code neds tobe debug.

Integration Testing
+ Integaption testing tet ingrato or interface between component, interactions to diferent parts of

thesystem suas an operating system, le system aná hardware o teas between tens.

+ Asaltertegatng wo ifren components together we do the iteration tes, As played the
Image blow when two diferent modes Mode A and Modul ar tgrate tenth iteration
testing done

of
Sofware Tsing Tang Moda |

29. COLE +

+ Integaton testing done by a spi integration tester rest tam.
1 neo testing lows our approach noun as

Top Dour approach

ono Up approach

gar approach

Cea Pr fst

Logical Organization of Testing

Na necessary how 1 any one!)

Big Bang Integration Testing

In Big Sang integration estr all components o module ae integrated simutaneouy afer whch everthing
IS teste asa whole As per the below image al he modules fom "Module 7 to ‘Module 6 te megrated
mana then the testing cated vt

ig Bang Approach

2)
NACE
ty 00 E

+ In ong integration testing a components or modules are integrate simulan, er which
Sieryhngistesiedasa what,

+ Inti approach individual modules ae no tegrated ut and unes al the modules are ea.

1 Bi Ban iteration testing ll the modules are integrated without performing any iteration testing
And tent’ tag ohne whether al he ineated modules re working feo ot

‘+ This approach is general executed by those developers who follows the Rn tad see approach.

+ Because of integra everthing a onetime if an are ocurs Ihn A become very dic fo the
programmers to now the rot ease of that re

E
far Ting Taming Module

30. 100062

+ Incas any bug re then he developers hast detach the integrated modules in order to fat actus
seo the bu
Advantage of Big Bang Integration
+ ig Bag testing th advantage that eveything fished before integran sing stars

Disadvantages of Big Bang Integration
+ The major dsadramae that in generas very tne consuming
+ tis very culto race th cause ofalurs because of ts te integration,

+ Techancesofhaing rca fuese more because integran athe components together at same
tine

+ Nanybugis found hen tis vry fut to detachal the modules inorder ond ut theoot cause oft
+ Tere ishigh probably of occurence ofthe real bugs the production envionment

Top-down Integration Testing

1 Testing tots place om top to bottom following th conti Row o architectural rare sure
from the GU or man mer), Components or stems ae substituted by subs, Blow isthe dagram of
"Top down Approach

topooun El
a E
EEE

Advantages of Top-Down approach:

+ The tested produc is very consistent Because the Intgraon testing ls basicaly performed in an
eaconment that amos mar at rely

+ Su can be written with ser time because when compared othe divers then Stubs ae simple to
author

Disadvantages of Top-Down approach
+ asc unctonalty ls testear the end ce

Bottom-up Integration Testing

Testing takes place trom the toto of the contol Row upward. Components or tems ar substuted by
ives Below the image of 'Sotom un appro

E
Bottom u E
> 7-7)

|
Sofware Testing Taie Module |

31. MODULEZ

Advantage of Bottom-Up approach:

21 ti approach development an testing ca be one together so hat th product or application wi be
efficent and as pe the customer specications.

Disadvantages of Bottom-Up approach:

+ Wecan cach they interac defects atthe endo eee
+ tis requied rate the test es or modes at al level excep the top control

FEE

System Integration Testing
+ iets the iteactonsbetwoen diferent stems aná muy be done str tem test

vers the proper xcuton of software component ad proper interacing Between components
within the slo,

+ Te objective of I eta to vlt that all oftware module dependencies ar fnctonay ore
nd a at Integrity maintain between separate modules forthe erie solution.

+ Aststing for dependences between ferent components sa primary function fSI Testing hs ares
hen most subject to Repression Testing,

System Testing

+ Insstemtestg the behavior of wholesiten/produtstestedasdetnedby the scope the development
projector pre

+ may ess base on is andfortenurement speciation, Business proces, ue cases or other igh
Jene sep of tem bsos tears wth he peat sts aná anlem resources

+ Sem ts is most often the fina test very that the stem to be delved meets the speciation
ands pure.

+ Sem testing crio by sect testes or independent estes

+ System testing house both funcional and nonfunctional requirements ofthe testo

Acceptance Testing
+ Aer the system tsthas corctod le most dels, the system lb dlmeredtotheuser or customer
foracceptace testing
+ capaces bash done byte sr or star though ote Saltos my bocinas el
+ Me gone acceptance tes o esta comience tr ten.
+ Aceptance tang is most often focused on vato yp testing.
+ Acceptance tang may occur oe than just angle ee for example:
‘+ A Commercial Off he shel (COS) software product may be acceptance std hen instalo
or negras

+ acceptance testing ofthe usability of he component may be done during component testing
Accetanc testing of anew funcional enhancement may come before sistem testing

Sofware Ting Taming Module

32. 100062

The type of acceptance testing are
+ Acceptance tes: focuses mailyonthefrctonaty thereby aidatig the nes dore ofthe system by
the business user. The user acceptance tests performed bythe wes and application manager
+ Operational Acceptance test: also known a Production acceptance tet valdates whether the stem
‘ews the requirements for operation. most of the organza the operational acceptance ti
performer bythe stem administration before the system reed The operational aceptance test
ma indude test of atup/retore, disaster recovery, maintenance tasks aná pride check of secu)
+ contrat Acceptance testing: Wis performed against the contrat’ acceptance ce for producing
custom developed software Acceptance shouldbe orally def when the contacts ares,
Compliance aceptance testing: tsa knowns regulation acceptance test performed gat the
regulations which must be ere such overmen, plo sty regions.

Alpha Testing
‘ia testing ane ofthe most common softuare etn strategies din sofware development specially
used by product development organizations.
Tits tes place atthe developer site Developers observe the users and note problems.
+ Alpha testing testing of an application when development about 1 complete. Minor design changes
ane made aa reat of alpha testing.
+ Alpha testing ype performed by prop that independent fhe dein team, but si within the
company. eg. house oftware tes engineers, sofware CA engines.
+ Alphatesting sal esting beor the softwares released tothe general pubic 1 hs two phases
‘+ nte fs phase o ala testing the sofware is tested by i-house developers. hey ue ether
debugger software or haare assed debugger The glist catch bugs qui
+ in th second phase of aha testing, the software is handed over o the software QA stat or
tonal sg an erironment hat smi othe ended use.
‘ia testing i simulator actual operational esting by potenti weseutomers or an independent st
team tthe developers ste Ala testing is on empoye fr ofthese sofware a a or of Intemal
acceptance esting. before the software gosto beta sg

During Development
+ oe

|
Sofware Tsing Tang Moda |

33. COLE +

Beta Testing

+ iis ho known as el testing tks plc at customer it. nds the ste to ses who int
and use under ea wer working conditions

‘+ Ata testis the secon phase of software testing in whch a sample the irtended audience vis he
product out (eta the second eter ofthe Greg alphabet) Orginal, the tem fa st meant the
frst phase of testing ina software development process. Te fst phase includes uit tes, component
testing and sistem sing. Beta testing an be considered preveease test

1 Te gral of beta testing to plc your aplican in he hands of real users cua of your own
einen tam to cover oy fw or sue fom the was perspective tat you would ot want 10
have in you ial release version ofthe paca.

Open and closed Beta:
Deveopesrelanse eher a dosed beta oan open bts
+ Closed beta versions are reset lc group finds fr a user est ard are tao owe

+ Open betas ae rom alge group tothe general publ and anyone interese, The ses repr ary gs
{tat they nd and sometimes suggest tna eures thy Wk shod e scada nthe rl version

Advantages of Beta Testing:

+ Youhavethe opportunity o get yur apicatin tothe hands of users prirto leasing tothe general
pub.

+ Users can instal test your appli, and send feedback to you during hi et tet pero

+ Yourbetateterscandlscoverisveswith your platon hatos may have notated, sch as contuün
pletion Now and even ashes.

+ Using the feedback you ge om these ues, you can i problems before i related to the genera
pub.

+ The more sus you that solve ra user problems, the her the qual o your plain when You
release tothe general publ

+ Hang a Mgherqualty appicaion when you release to the general pub wil crease customer
ation

+ Tese users, ho are ey adopters four aplican, wil generate excitement att our appli.

V Testing concept
+ it ocean Continuous testing throughout the SLC
+ Goes hand hand wih formale tem development process
+ Need to pln the testing actives pra wth the SC phase

E
far Ting Taming Module

34. 100062

Sftaare testing hs raw become an intel pr ofthe software development process. The formal models
software development and testing made whieh eps ery need of planning and design oftestingin the ery
Stage of development process. Oe ams of V mad our conventional waterll mode whereas anther arm
AV shows corresponding testing methodology required a each phase of development process.

The major Benet of having bth SOL along with TL Is ha, testing and development both get equal
Importance in the proces nd forces management or their comment, attention and planing of requires
resources equal for both,

‘Another important advantage hat, output rom the development phase can be tested or reviewed by estos
‘The last bt no st, cry planing of testing process giant reduces non canermies which otherwise
not detected at th rep pases

V Model

V model means Venfcaton and Validation model Js Ike the waterfall moda, the Shaped Ife oe ia
Sequental pathol exon of processes. ach hase mst be completed before the next phase begins Testing
ofthe producti plamedinpralel tha corresponding phase o devlopmentin Vol

Requirements te BRS and SS egin the He cycle model jst ke he water model ut ini model before
(evlopmen started, asyiemtesipaniscrete, rete an uses on meeting thefunctonalty pocitos
inthe requrements terio.

‘The hgh eve design (ho) phase focuses on stem architecture and design. provide overview of solution,
platform, sistem, produc and servie/ process. An integration est lon is erent ins phase as well more
totes the pics ofthe software systems aby to work together

The lowievel design (UD) phase i where the actual oftware components ae designed. 1 defines he actual
loge for ach and every component ofthe stem. Class dagram wih al he methods an relation been
classes comes ude LD Component ests ae ecatedin ths phase as wal

‘The implementation phases, pin, where alcoi abs plate. Once coding complete the path of xeon
ensues up he ght ie ofthe V where the et plans developed eater ae now pet toe.

Coding: This atthe botom ofthe Shape model Module designs converted it ode by develope.

Advantages of Vimode!:
+ empleando tou.

+ Testing activities planning ts designing happens vel bete coding Th ses ala of ine Hence
pr chance of sucess ove the tell mode.

Proactive delet racing = has detects ae fund at ay stage.
vod the downward fw ofthe detect
Works wet smal projects where equtererts ae easly understood,

of
Sofware Tsing Tang Moda

35. COLE +

Disadvantages of model

+ ory pd and east abe
+ Software i developed during the implementation phase, so no car prototypes of the software ae
produces
+ Nan changes happen in mia, hen he ts documents along wth requiere documents has to be
updated
When to use the Vimodel:
‘+ Te vshaped model shuld be used for mal meds snd projet where requirements are dea
eine ond ed.

+ TeV shapedmode shouldbe chosen whenampetechicalescucesare anal trece echa
eerie

’
(0) oa

38. 100;

SPECIAL TESTS MIN

+ Reauiremenstestng
+ Usable
+ Contguation testing
+ Compa esto
+ instal testing
+ Location & nematonstzaon
othe special tests
+ Represontestng
+ Res,
+ Smoke testing
+ Sanity testing
Species stems
+ Gent server stems
+ Web kasd stems
+ Deseo stems

Requirement Testing

equrement-bsed testing ls testing approach in which test cases, conditions and data aro dried
from elements, includes functional tests anglo nonfunctional aires such as perormance, lb
or usa ti testing. the proces stars rom requirement phase and continues unt epeation and
mantenance phase
The objectives of requrement testing ae

+ Toimplement he wer request

+ Tomaintainthe comets

+ To ensure the procesing complies with organisation's poles and procedures
‘The methods used tomeet he ajecies are

+ Creation à matt determine whether al tequrements ae flied

+ Use of cect to very wheter stem meets rana! pois and government regulations
The usage of stare testing

+ ensure that stem perorms comet

+ To ensure that oreciness canbe sustained for a considerable perio of tne

+ Toensure tat the sem canbe tested for coins though al pases of SOL but In case ofrelainy

‘the programs shouldbe In place o make stem operation

Installation Testing

Insta esting ia ind of ety assurance workin the sofware industry that focus on customers
wil ned to do tinstal and se up the new software suce The sing proces may ive fl paral of
parades nsal/uisal processes.
I detemines wheter:

+ Te installation procedures documented

+ The personel retrained ininstaliton proces

+ Te methodology fr migration rom ld stem to newsystem documented

Je (
Sofware Testing Taie Module |

39. MODULE

Into tes wl check the instalation and coffuraon procedure wl a ay ising dependences. The
del saliston might simply appear tobe run a setup program, the generation ofthat setup programs and
ls heat ina varity of machine and operating stem entronmerts can requre eens testing ble en
be used with confidence. n stud systems, particulary where software t e released It an lead)
I target emirermen (sth a an operational web ste instalation (or deployment sits sometimes cated)
Can ile database schema changes a wel athe instalation of ew soto A fc hat can rene
‘he orgaiztonal requirements of such an exi need o synchronize the ata nthe fest ployment
moment wth that nthe he eminent th minimum ruption ove operation

Usability Testing

ray test, non unctonal testing technique ht a messe of how est the tem canbe ute by
end users. es fil 10 evaluat and measure ut canbe evaluated based onthe level o Sil equted to
esse the software ts performed est the cae of in an apple.

determine

+ How simple ts to undentandappeation usage
+ Howeasyitisto meute an applcason process
+ Dect absent of people using the stm
+ Usb surveys
In designio salt flowing are the important questions tobe aha
+ Money ti fora user uo has never seen the product before to cary ut base aks?
+ Mowessyit ui fr the user who as used the product before t remember howto cry out the sme

‘ose?

Howell and feet wii for ser hos used the product before 1 qui cry out frequent
per]

+ How goods the user experience in sing the product?
checks or man factor problems ke:

Ar outputs meaning
Ar or dignos sion?

Does have conf pata, comer, format, se abbreviations?
It enstouse?

+ lsthre an ut option all choles?

Ishoudnet

+ Annoyimendnd user infuneionorspeed
+ Tote contro the user vincia wen tve retuned

tol

+ Prode enone help oruser marl
+ Se constemintsfuncion and overall design

User Interface Testing

Ins porform to check hou user any the apleatonis. Therefore the interacts the process f testo
products graphical ser interface 1 ensure meets ts pein. hiss normaly done tough house
fat of et eases

Sofware Ting Taming Module

40. 100;

Ie etermines wheter:
+ Aoproprte input hpi played ren
+ correct messages ar played when an errors enteres
+ Columns hve meaningful names
+ Navgaton within the applications easy

1 shoud be performed without the sstance of the system personne lective UI dens one that proves
the highest usb tothe ers

‘Thefoiowing design elements ae important nis testing process
1. Tetester shouldbe avaro existing cl schemes and standards
2. Te tester should be aware of object sng such as ht and width of various sree ems. Example -

stand er solar tht they are required be eleven pas wie oe application hs à nine pe
wide seottor when the nd st leven, then is a ont aná shou be ige

3. em aná obje le spacing ae ther important standards that hau not be gored. Han tem le
rot eect aces, then other app nconssteney ste resul

5, alldescpon fel have the naming convention of descr andthe name inthe plan is description
then ista quals 3 bu

6 Las but ot easton the GU desig standard Near fimporance are font ses and types ect
es af thi if the les tobe uppercase Times New Raman fr a tn poi itch nd he
plan as ower eat les ofthe same for, then.aicrepaney ha ran

Performance Testing

Performance testing Is the process of determining the speed or efkciveness of a computer
network, software program ar device. This proces can mode quartatwe tests ope in ab suchas mensura
‘he response eme othe number of MPS (lios intros per second) at which tem funcions
Load

toad determines response mes of ital business processes and transaction to determine whether they re
within documented expectations

4
Sofwar Tsing Tang Moda 1

41. MODULE

Stress
Stress determines the load under which atom fos, an how it fa

© ators ©
Configuration Testing

Configuration testngsthemethodoftestnganappaton with multiple combinations of software and hardware
to ind ou he optimal configurations thatthe stem an work without any as or bus determines the
(ect aladdin or madiing the resources such as

+ Dies
“au
+ Networked
‘The purpose of configuration testing Isto tet for compil les, determine minimal and optimal

(ran of haare and software, and determine the eect fading or man resources uch a:
‘memory dk eves and CPU

Configuration esting easy wih most automated test tas Because sept are resale and can be easly
run on ire pleno, Testing Brent stem contrato or deen tems y ruming the same
rend and comparing response tine

Configuration Testing

’
(0) Omar

42. 100;

Compatibility Testing
ompatbitytestogis type ofsofware testing sadto ensure compatbity ofthe sjsten/appcaonweste
but minos eter bjs such other we browsers, hardware plans vers incase dws wey specie
typeof requremert, such sa user who speaks and can ead ony a parlar language), operan sas
te Ths ype of esting els And ut how well a stem peros a partculr enorme ha ines
Farre, network operating stem and eier software et

It silo malo test is performed to ensure that application encon propel on multiple
system contes, more giant where any browser can be used 1 aces the aspcanon

Usage
ompatbity testing determines an applcaon under supported configurations performs as expected wth
Varios combinations ol hardware ar sofware vous and ee

Example:

Configuration system would salt that a web application supports a browse (of specie configuration),
(Company testing would determine which vendors under he same conRgration are compote wih the
‘web aplcaton

Compatibility

Localization and Internationalization

I pe of nonfunctonl est
Internationaeatonisapracess of designing a software appcaton so that canbe adopted to arios languages
an regan without any hares

Whereas Localzaton i process of adapting ltenatonaed sofware for a specie ren or langue by
nga specie components and rasa txt

Localization:

‘The aspect of developmen and esting relating othe transation of he Sftare and resentation othe
end uses Thi includes tant the progam, choosing appropriate cons and paphis, and othe curl
ensideratons aso may icude ansia the rogams el les ad the documentar

‘The aspect of devlopment and testo related to hang orig txt and ata thin program. Th inte
sorting, porting tex and dts, correct handing of currency an date and time formats, tng paring upper

4
Sofwar Tsing Tang Moda 1

43. A

ander case handling, and so fr. lo includes th task of separating sings ram the source code, and
making sure at he foreign language Sings have enough spac In your user iveco tobe spayed corey

Regression Testing
Bresson tes type of software tesi vers tat sofware wich was previous developed
nd tested 8 performs he ame way er as changed or macs wth other sofware. Changes may
Ince ar nhancements, patches, configuration change

en an moon or changes are dan othe patin or eve when ay smal change i done 1 he
code he cant rep sue, Along wth henechnges becomes ey impartan tet whether
{needs unconaltyi actor not. Ths cante ace db dig the regression eng

+ The prose ofthe regesson tesingso And he bugs which may et reduced accidental because ot
new change or mode

+ Duingeonftmatentestngtbe defect gt edad that pata te appatin started workings atende
Bu here might be poly tat the may hve Introduce or uncovered a erent eet eur
Inthe sofware The ay to detec these ‘unerpected efect of fae st do regression testing

+ Tisaoensres thatthe bugs fund crio ae NOT retable.

+ Usa the eresion teste done by automation ols because in order tof the defect he same est
ardt agan and again nd wil e very tedious and te cosumingto do manually.

+ During eresson testing the test cases are ltd depending upon he changes doneto the fate or
rade nthe aplican. The fsur o made where the changes or motto den hat entre
Teure an o print or et

+ Tis ting becomes very important when there ate conti us modas or enhancements done
inthe app or produc. These changes r enhancements should NOT ioe new ses in the
sto tested cove.

+ Tis els in mami the qualt ofthe product along wth the new changes ne aplicacion.

Retest all

hegreson ati (— Neon tet

Prioritizationot
Test Cases

Types of Regression Testing:

‘There ae fur types of regression esting techniques. They area flows

+ Corrective Regression Testing: Corrective repression testing can be used when there sno change inthe
‘pecteatons andes cases canbe reuse

+ Progressive Regression Testing Progressive regresion testing is used when the modifications are donen
the spcieatens ang new tes cases ar designed

;

44. 100;

1 Rots. Strategy The retest a strategy is very tedious and tne consuming Because ere we ree a
test which ests In he execution of unnecessary test cases. When any smal modification or change is.
(one tte appt hen hs state at wet

+ Selective strategy: Insletve strategy we use a subse of the existing et asest cut down theretesing
‘fort and cos. ay changes are done to the program ents, og Tunchon, variables ee, hen 3 et
Unt must be rerun Here he afi pats o And ot the dependencies between à test ae and the
program ets towers.

Advantages of Regression testing:
+ hou tomake sr tat ay changes bugis any enhancmetst the module or platon
have ot impacted the existing ested code
+ Remus ht he ug found rer ae NOT cet
+ Regresiontetngcan be done by using the automaton tools
+ pin improving the ult he roe.

Disadvantages of Regression testing:
+ rearessontetngs one witout ing automated took then can be very ius and me consuing
cause ere we ut the ame et Fe cobs gan nd a.

‘+ Regression testi required even when 3 very smal change 3 done in the code Because ti mal
modifican can bring unexpected sues inthe sist function

‘Smoke Testing

Smoke testing ia ype of far testing which esures that he mao funcio aplaton are
working fie Ths testo slo known as Bad Veran esting’ no este testing wth very
ated test caes o ensure that he impartan features ae working ead we re god proceed with the
rales,

‘Theta smoke’ testing soriinatetrom the hardware testing, wer device when st sched ons tested
forthe smoke o re fort component. Tisensures tat the harduare ba components are working Be
nro rules found.

Sec, hen we do smoke testing ofan application then this means that we are trying 1 ensure that there
should NOT be any majo ales before ping the bu for exhaustive testo

Advantages of Smoke testing
+ tes nina the bugs inthe ery stage of esting
+ Ip nina to sues that gtinrodoedby he integration of component

+ Rhein vesting the sue ed in the previos bl ae NOT impacting the major functors o
the appicaton

+ Voy tinted number of test caes is regule to do the smoke testing.
+ Soke testing can be cae out in smal ne.

N
Sofware Tsing Tang Moda

45. MODULE

Disadvantages of Smoke testing

+ Smoke testing does not over th deals:
+ tesa noneahaustve testing with smallnmber of test caze because of wich not ar bl to fad he
‘ther ee ues.

a=

48. ES MODULE 4

TESTING PLANNING CSSS

IA software Tes Plan à document descbig the testing scope and ates. te ba fo formally
Fest am ste frodctina project uses abot jects copo, erent eters, approach, nv
‘oles responses, sches, sk are the mitigation, pr, em ps eerie
Wyo pln amine

+ You lan thse things that you know are more complicated than what you ando

You plan things or which ode and completeness are important

You Plan things when know that current industry standards are tested andreas software averages

more than en ica bus pe 600 ines of ode
+ Youplan to ik head and plain your testing one way to ct that down

@ Test Plan

+ Test planning & control
+ Define activity of each testing level
+ Define milestone ‚resource ‚schedule,
+ Make a plan based on analyzed risk factor
+ Define test stateoy based on risk

+ Define approach & techniques for testing
(esting techniques, coverage, test tem, test
ware)

+ Define completion condition

Test Plan
Iris à contact between the testes and the project team users describing the roe of projet team users
describing the oe of testing nthe projet. Ths stag i whee a of the work nave in planing and set
Pas of. escribes the way a which we wl how our custome thatthe software works comet. Aso
plis who does the testing wy the ss ae performed hw the et are conducted and when the tests
mere)
test lan tats wat he ems o be ete re at what vl he wie sed, hat sequence they a tobe
tested how the es sratey wil be apple to the esting of ac item describes the tr enaronment
test plan shoud ial be rgniaton ide, Bing applicable tol the organisation sofware development
‘The objective ofeach test plan to provide a plan for vrscaon, by testing the sota I the sofware
Produced fal the functional or design statements ofthe appropriate sofware speciation Inthe case of
xceptnce testing and system testing this generly means the functional spect
‘The test plan answers such ess at

+ Whats being testa?

+ What ar pas/a rte?

+ Wan nchtest occur?

N
Sofware Tsing Tang Moda |

49. MODULE 4

+ what hardware and software eones required?
+ what features must tested?
+ What ar the responses of Inland organizations involved inthe project?

TEST PLAN

<<<

Test Plan Template

+ responden

+ Testscope

+ Testobjcves

+ Assumptions

+ anal

State

Features to be estee tobe tested
oes nd responsibies
Test schedule and resources

+ Communication approach
+ estos

Test Plan Identifier
Is auge enr rte ts plan vi versione whch we ae rear lo

Introduction

"Overview of System x”
Purpoie of hie document”
"This document intends to serve as the af test approach fr the business stems development project
Preparation fort est condo tee major ages
1. The ts approach sets the scope ste testing the vera strategy to be adopted he ates
10 be completed the genera resources required and th method and processes to be used 1 tet
the elas. aso deta the aces dependencies and ello required o conduct he system et
2. Testplansing detaisthe atts dependences ad lot requires conduct he system est
3. Test condon cases document he tests o be applied, the dt tobe processes the atomos
testing coverage andthe expected esas

(2) Om

50. ES MODULE 4

“Formal Reviewing”
There wi be several forma review ponts before and during tetes Ths stl element inachieving
ay product

Test Scope
Answers wo important questions
+ What tbe covered inte test
+ what i not beconvertedin the et
Ines.

+ Functional or seta requirements
+ Sem inerfaces
+ Aspicaon documentation

Test Objectives
+ Conbesimly calas Testing oat
+ Guides development test caes, procedures and st ata
+ Tester andproject manage can gauge tes progres
+ Enhanc communication bth within an utile of the projet team hein 1 define he scope ofthe
testing eto
ample ope

The colega sports pain astm wä be uni tested and astm tete. Un tests wll ares functional
qua, we sem testing wl addres sues of ealbityandpertomance

‘Theineracton ofthe subsystems wile tested as flows
Content management to paga
Content management reporting
Teen stems intertces wil be tested
Cait ports aang stem to exiting WebNewsDatine We Serer
Collegiate sports ating system to pain gateways
The master testing willbe that of ad and performance esting Ths wl be adresse solos
We irate ates scenario that wl generate increasing numbers o apes 1 200,00
We wit ao erese test sensi tht has new content ring a he stem at the at of ne om every 20,
Seconds Las, we wil sinloteinceasing concent subscribe leas up t 200000 ts a statement of what
theteserisexpetedto accamgah or alte dung aspects ay et object includes gh el
description of expected rests m measurabe terms aná sprite

Assumption
Document st prerequisites, wich not met could have negative Impacto the test
Sample:

+ Säle of resources

+ Testbudget

2 Sat of apa at art of testing
st ut eli assumptions which ae used as bass fr test planing

of
Sofware Tsing Tang Moda |

51. COLE, 4

Risk analysis
Document et ska ther posi impact the test fort
Sample
+ Newteehooogy
+ Sequence aná incromerts ol code ely
+ labo ppeation test resources
den what share st o tested and what the real aras are, such a livery of thi party product
+ New version ot intra sofware
+ ly ous and understand anew pctage/too ete
+ Exremeÿ complextunctons
+ Moston to components tha pastry flute
+ Poy documented modules or change requests
‘There are some inherent sofware sks sucha comple; thee nee to be dene
+ ste
+ GoVermentreglatos and ls

Strategy
‘The strategy ou deny mjor tes aces andthe methodology employed terete he et aces
+ Overall approach of testing
+ lack Bor
+ Typesevlsottens
+ Unt iteration
+ Secures
+ Mayor aces
+ TestEnvronment
+ reos

Features to be tested/not to be tested:

Features to be tested

"This Ein tha it be tested om the USERS vewpoin of what the stem dos. Thi nat technical
desriion ofthe software, but USERS view ofthe funcion

'
QE

52. ES MODULE 4

Features not to be tested:

ii à ing of what is NOT tobe tete from both the user viewpoint of what he system does and à
contraten managemert/version contol vew

Roles & Responsibilities
1 eines who esponsie fr each stage of testing and generates responsibilty mari
foe Test designer

Response:

generate test mode

+ Toeralteetlectvenes often eos

oe Tester

esponsibities:

+ To document change requests

Test Schedule and Resources
Test Schedule:
‘test schedule cues the esting steps rt, the target sat and ed dates, and responses. shuld
ho describe how the est wl be reviewed racked, and approved. soles

+ Major test acter

+ Sequence tes

+ Dependence onthe project actes

+ nal estimates foreach city
The Planned Resources nude People, Tos and Facies.

N
Sofware Tsing Tang Moda |

53. COLE, 4

‘Suspension Resumption Criteria
Sspension eters speciy the cera 1 be used to suspend aor a portion of he testing actes while
resumpon eter spec en test an resume ater has Been suspended.
+ Unai o externa dependent systems dung exciton
+ Wena detects introduced that cannot alow any further estr
+ Coca pa deadline misses tat he dent wil no ace delivery even les completed
+ Aspect halay sus down bth development and testing
System integration Testing he Integration envionment maybe resumed under the flowing ctcumstances:
+ Menthe external dependent stems become arab gin
+ Wena fis success Implemented and the esting team notified to continue testing
+ The comractisrenegotted with the ceo extend every
+ The hold period ends
Suspension criteria asumes that esting canot orard and hat gin backward is ao nt posible A led

bul wold nt seat ys cou generally conte to uo the previous bul Most mao rra eects
wuld ao not constuted suspension cea as other areas ofthe Sistem cul continue tobe ested

Test Environment:
Fortes erionmen, ny are oe up indus:

+ Sytem and apts

+ estate

+ Database server

+ Front nd runingenionment

+ Glen operating tem

+ Hardware tudes Server Operating stem

+ Documentation ll reference documerts/cofguraton guides instalton guides wer manual
[testing envronmentis a setup of oftware and harduare on which he tes tem wil conduct the testing
Few challenges while seting up the test envionment ar:

+ Combined usage between teams

+ bora setup tine

+ Inle planning for resource usage for iteration

+ Complets configuration

Communication Approac
+ Formal and formal meetings
+ Wong sessions
+ Escalas procedures

E
far Ting Taming Module

54. MODULE 4

Test Tools

Teal ae those which are neded to support he testing proces, Tos ar sed or:

Test management
Configuration management
Stress/oad testing tots
Det king oo

Any too hat wl be needed to suppor he testing process hou be included here. The infomation ovtined
here canna usa be completar once, ut capturedin eater eves of eta the projet progress
Fou he ite ye

y

Sofwar Tsing Tang Moda |

55. COLE, 4

Importance of Test Plan

A test lan isa tale document hat outines the st sate testing object, eures (manpower,
‘Sofware, and hardware) rege o ts, rt schedule, tet mon a te der be sere a
luego conduct sofware testing actes a dened proces which minute mentores aná control
bythe est manage Mang et Plan hs mle Denes

+ Test Plan help us determine the sor needed ovate the qual ofthe applaton under test

hop people outside the test tam suchas developers, business manages, customers understand the
desi of testing.

‘+ estan guides outing. sie are book, which needs to be flowed,

+ Important aspects he ts estimation, ts Scope test strategy are documented in Test ln, so ean be
rene by Management Team and re-used for other poet.

How to write a test plan:
Vos ad, now at malig Tet Plan the most important ak fet Management roces Flow he
devon sop teow oc it
isthe prod
Den te Tessa
tn sota
Det ee bats
eue Pang

A
s

idelines to develop a test plan:
+ Surteaty

+ ep the est lan este

+ Frequent review the ts plan

+ keep the es pla conse and esa

+ Cale laringe

+ Spend the time tdo complete test plan

'

58. 100;

TEST DESIGN SE

tes designs the ac of resting and wi tet utes or testing sfr, Test ana ad dem st
conan ies usa generic fr testing wich covers que a re range of posi, ut when we come
To make a testcase we need 0 be very spec I act now we need the exact aná dealed spec put But
Just hang some vals to nur tthe system spot test you dont know what the stem supposed todo
‘ith the input, you ml not be abet el that wheter yur test ha pated or led

More than the ct of testing, the act of dering tet is one ofthe best bug presenters known. The nin
that must be done to create a usa tes an discover and eliminate bugs before they ar cadedineed es
design tiki an scone and elminate bugs at evry stage the creation of software, ram conception to
peche, to design coding and the et

Objectives:
+ Turenne since of et een
Totnow the deta of tet cae wing
Towite godt oser
Tente common esas mies
Tos the contents ofthe es se
Teen Lang teh eee dis buy vu na ee
+ Tomangeten ota

Importance of Test Design:

Foundation to design and develop tes bt
Greer confidence nasty
Completeness of test

+ imation of te font

of
Sofware Tsing Tang Mods"

59. MODULES

Test Design Essentials:
+ sens overall etues
+ Tete isa Balance between norma, abnormal, boundary and environment est ses
+ Tete isa lance between Black box a white bates
‘+ Tete iss lace between funciona tests and non functional tse
+ Fray, documented test caes

(ce ts design aay to success for many organizations andfor the project. Ding est avs ges you
a chance to anand the speciation rom deen angles

Youcan repeat the same test cases
Someone cn ess the et ass or you
date the quay fet cases
Estate the quit ol target star cry

What is a good test case?
shoud be accurate and do what itis intended to e

No necessary steps shouldbe ined nit

shoud be evsabe

should e acabe 1 requirements.

should comptant regulations

shoud be Independent Le. vou should e able o erect in any order without ny dependency on
mereces.

It shoud be simple and cla, any str shou be abe to understand by reading one.
"Now keeping mind these characteristics you can wrt goodand elective test caes

2

(5) o

far Ting Taming Module

60. 100;

TIPS for writing good test cases

Tests only one thing

‘Always mae sure that your test se tess only one thing, y yo test mp conos mone test ast
becomes ery fit 1 rack els and ers,

Organize your test cases consistently

‘ou can oran your test ass in many ways however yu should always follow he same pattern 1 organizo

te independent test cases

‘our testcase should not hive dependency on the ts ses, Le ou should able 1 este you test ase
Inada with having dependency on other tes ae

lite small test cases
‘Aisa mention purpose of ach tet case ay intestate
long things hou be latin mind whe wing the good et ae
+ establo test
+ tem displ th, does that
+ Spl conversational language
+ fac content name of lls not generic
+ Dont ein windows bases
+ Order of ae follows busines senator

How to write good test cases
proving testa of tet cases
tas to execute he test and whether the tester has 10 pt afin during the testing process
+ Accurately means thatthe tse followsthe direction, the esl of pas or fa wl be cone
Improving testa wth language
+ Teststeps shouldbe wrtenin athe case. Tel the tester what to do.

itil]

li

4
Solar Tsing Tang Moda

61. A

At othe shopping ar page

Compare the tems inthe ar withthe screen capture

Chek on con

It shoud always be dar whether th testers doing something ore sistem doing
este reds, "The button pressed” does hat mean he or she shoul press the button, or dest mean
over that the system plays tas red presses? One fetes ways confuse tester to mix
up actions and ests In ure actions aways goon the lt ide, ests ont ige Sid, What he
tester oes salvas an con. What he sistem pasar does says asa

Y Enternew name and address. Press <OK>

‘splays cren COB new name deals

i ak wth natura data Make screen gab

‘splays screen 005 maintenance, Press <OK>

3 leon nai bation Bilas sere 009 ui deta
4 Enter name rom seen gab Press <OL> Dip ren O10 record detal
5 Compare record deta wth screen rab An deal math each

nee tet case stes the along ceria
+ Reasonable probatty of cai an enor
2 Does not dounnecesso things
+ Nether 10 simple nor oo complex
+ Not redundant wäh other ete
+ Makes fares obvious
+ ows slo ad nikon of ros

Test eases as development assets have a fe beyond testing. They represent complete picture of how the
software works writen in lin Engl. Even ifthe focus s destructivo they must abo prove that al business
canarios wrk ar required Often the cases ae write for testers who are the busines user so they ue el
range an ems Ast of we css as tremendous value 1 others who are working tern ars

este
+ Guiness ses
+ Hp desktecticans
2 Sales and martin stat
+ Web administrators

’