software testing and quality assurance .pdf

Handout

1. Software Testing &
Quality Assurance

2. Introduction to Software Quality & Assurance
Unit No. 1

3. Introduction

4. Objectives
After completing this session, you will be able to:
▪Define Software .
▪Define Software Quality Assurance.
▪Explain Software Quality Challenges.

5. Introduction to Software Quality Assurance
Bus. Comm.
▪The intelligence in totality that you provide to the computer system in order tosolve your
problems is software.
▪It is a set of instructions (program) and related data that guides the hardware and tells it
what to do and how to do it and how to accomplish each task.
▪Everythingthat“runs”onacomputerfromanoperatingsystem,programming
languages–machine-level,assembly-level,high-level,languagetranslators–
assemblers,compilers,interpreters,platforms,frameworks,documentationtoa
diagnostictool,videogame,orappissoftware.

6. Introduction to Software Quality Assurance Cont ..
▪The software plays a key role of a mediator between the user and the computer
hardware.
▪Itisaninvisiblecomponentofacomputersystemthatmakesitpossibleforyouto
interactwiththecomputer’sphysicalcomponents.Itiswhatallowsyoutocommunicate
withsmartphones,tablets,gameboxes,mediaplayers,andsimilardevices.
▪Softwarequalityassuranceisdefinedas:
-Allplannedandsystematicactionsnecessarytoprovideadequateconfidencethatanitem
orproductconformstoestablishedtechnicalrequirements.
-Designedtoevaluatetheprocessbywhichtheproductsaredevelopedormanufacturedit
isasetofactivities.
6

7. The Software Quality
▪SoftwareQualityiscentraltotheentireprocess.Thesoftwareshouldprovideeaseof
use,stabilityandshouldbegoodfittoactualneeds.Qualityisoneoftheelusivethingsof
life;youcanknowitwhenyouseeit,butdonotknowhowtocreateit.
▪Weknowhowtodefinequalityandhowtoachieveadegreemuchgreaterthaninour
ownpractice.Difficulttomeasure.Evenreasonablequalityrequiresadequatetesting.
▪SoftwareQualityAttributesforProductOperationare:
1.Correctness:Thedegreetowhichaprogramsatisfiesitsspecificationsand
accomplishesthecustomerrequirements.
7

8. The Software Quality Cont ..
2.Reliability:Thedegreetowhichaprogramisexpectedtoperformitsenvisionedfunction
withrequiredaccuracy.
3.Efficiency:Toperformitsfunctiontheamountofcomputingresourcesandcoderequired
byaprogram.
4.Integrity:Thedegreetowhichaccesstosoftwareordatabyunauthorizedpeoplecanbe
controlled.
5.Usability:Learning,operating,preparinginputandinterpretingtheoutputofaprogram,
usabilityreferstotherequiredefforts.
8

9. Product Development & Production
▪ProductDevelopment
▪ProductProductionPlanning
▪Manufacturing
-Duringtheabovephases,defectsinanindustrialproductcanbedetected.
9

10. The Software Quality Challenges
BasicProblems:
HighComplexity
Invisibilityoftheproduct
LimitedOpportunitiestodetectthedefects(bugs)
Challenges:
1.UnstableEnvironment
Usually,QAteamsfaceunstableenvironmentsetupissuesthatweneedtoprepareformost
ofwhatwehave.Sometimestheservergetsstuckduetooverloadandrequiresarestart
manytimesduringtestingetc.
10

11. The Software Quality Challenges Cont ..
2. Tools Being Force-fed
Nowandthen,werealizethatatoolisnottherightchoicefortheproject.Wedonothave
anyotheroptionbuttokeepusingitbecausetheclients/organizationalreadyhavelicenses
andwouldnotgoforanewoneuntilthecurrentlicenseexpires.
3. Tight Deadlines
The biggest challenge QA is to receive requests for last-minute testing. The primary reasons
for such demands are that the development process takes more time than expected and the
time for testing is underestimated.
11

12. The Software Quality Challenges Cont ..
4.TestingDocumentsCreatedByOthers
InthecaseofQA,it'sfastertocreateadocumentfromscratchthantousetheonecreated
byothers.Usingtestcasescreatedbyothersincreasesthetimeofverificationandputs
limitsasfarasdiscoveringbugs.
5.WrongTestingEstimation
Whiletryingtomakeanaccurateestimate,somesoftwareestimationscouldbeentirely
unpredictableandgowrong.Asdevelopers,QAalsodoesn'thave100%securityfrom
unexpectedissues.
12

13. The Software Quality Challenges Cont ..
6.FixingBugsDuringTesting
DevelopersandQAengineersshouldworkclosely.Testingshouldbedoneoncepartofthe
developmentprocessisdone,andafterthat,bugfixingactivityshouldstart.
7.Last-MinuteChangestoRequirements
Itisslightlycommontochangeprojectrequirementsmid-sprintinagiledevelopment
projects.Whilethiscanbefrustratingfortheteamandduetothattesterscanbeaffected.
Theymayneedtore-trythewholeextentoftestingsinceeventhelittlestchangestoa
codebaseshouldbegonethroughvariousteststoguaranteeitssteadinessandsimilarity
withexistingcode.
13

14. The Software Quality Challenges Cont ..
8.InsufficientCoordinatedEffortAmongDevelopersandTesters
▪Professionaldifferencesbetweendevelopmentandtestingteamsarestillcommon.
▪Developersthinkthattestingisafinalprocessofthesoftwaredevelopmentlifecycle,and
testersdonotrequireanythingapartfromalistofuserjourneysandtechnical
requirements.
▪However,testersmayhavedifficultyidentifyingflawsinthecodeiftheyarenot
acquaintedwiththedevelopmentprocess.
▪Iftheydonotunderstandhowthesoftwareworks,theywillhavetroublecreatingtest
casestofindallpossiblebugs.
14

15. Software Quality
Thequalityofsoftwarecanbedefinedastheabilityofthesoftwaretofunctionasperuser
requirement.Whenitcomestosoftwareproductsitmustsatisfy the following Factors:
1)GoodDesign–It’salwaysimportanttohaveagoodandaestheticdesigntoplease
users.
2)Reliability–Beitanysoftwareitshouldbeabletoperformthefunctionality
impeccablywithoutissues.
3)Durability-Durabilityisaconfusingterm,Inthiscontext,durabilitymeanstheabilityof
thesoftwaretoworkwithoutanyissueforalongperiodoftime.

16. Software Quality Cont ..
4)Consistency–Software should be able to perform consistently over platform and
devices.
5) Maintainability–Bugs associated with any software should be able to capture and fix
quickly and news tasks and enhancement must be added without any trouble
6) Value for money –Customer and companies who make this app should feel that the
money spent on this app has not gone to waste.

17. Software Quality Factors Management
▪Softwarefactorsarethefactorswhichinfluencethesoftware.Thesefactorscanbe
classifiedintotwocategories,theclassificationbeingdonebasedonmeasurability.
▪Thefactorsthatcanbemeasureddirectlysuchasnumberoflogicalerrorsisthefirst
categoryandthosefactorswhichcanbemeasuredonlyindirectly,forexample,
maintainabilityisclubbedinthesecondcategory.
▪Tocheckforthecontentandthequalitycontrol,however,eachofthefactorsaretobe
measured.Thefactorsofqualityare:

18. Software Quality Factors Management
▪Correctness:Degreetowhichaprogramsatisfiesitsspecificationandfulfilstheclient’s
objectives.
▪Reliability:Degreetowhichaprogramissupposedtoperformitsfunctionwiththe
requiredprecision.
▪Efficiency:Toperformitsfunctionamountofcomputingandcoderequiredbyaprogram.
▪Integrity:Degreetowhichaccesstosoftwareanddataisdeniedtounauthorizedusers.
▪Usability:Laborrequiredtounderstand,operate,prepareinputandunderstandoutputof
aprogram.

19. Software Quality Factors Management
▪Maintainability:Tolocateandfixanerrorinaprogramtheeffortrequired.
▪Flexibility:Tomodifyanoperationalprogramtheeffortneeded.
▪Testability:Totesttheprogramsfortheirfunctionalitytheeffortrequired.
▪Portability:Toruntheprogramfromoneplatformtoootherortoodifferenthardwarethe
effortrequired.
▪Reusability:Degreetowhichtheprogramoritspartscanbeusedasbuildingblocksor
asprototypesforotherprograms.
▪Interoperability:Tocoupleonesystemtoanothertheeffortrequire

20. Software Quality Factors Management
There are various ‘checklists’ for software quality:
▪Functionalitybyevaluatingthegeneralityofthefunctionsthatarederived,thefeatureset
andtheprogramcapabilities,andtheoverallsecurityofthesystemthisismeasured.
▪Usabilityisassessedbyconsideringhumanfactors,overallaesthetics,consistencyand
documentation.
▪Byevaluatingthefrequencyandseverityoffailure,theaccuracyofoutputresults,the
meantimebetweenfailure(MTBF),theabilitytorecoverfromfailureandthe
predictabilityoftheprogramReliabilityisfiguredout.

21. Software Quality Factors Management
▪Bymeasuringprocessingspeed,responsetime,resourceconsumption,throughputand
efficiencyPerformanceismeasured.
▪Theabilitytoextendtheprogram,adaptability,serviceabilityorinotherterms
maintainabilityandtestability,compatibility,configurabilityandtheeasewithwhicha
systemcanbeinstalledarecombinedinSupportability.

22. Software Quality Factors Management
▪Aseriesofplanned,systematicsequentialactionsthatenablethequalityofsoftware
producedisSoftwareQualityAssurance.Allsoftwaredevelopmentunitsusuallyhave
theirownSQAteam.
▪ThisSQAteamtakescareofthequalityatthehighendthatistheoverallproductandat
thelowerorderthequalityisthesoleresponsibilityoftheindividualwhomayengineer,
reviewandtestatanylevel.
▪Acharacteristicofthesoftwareproducedmustbesoftwarequalityandthusrathertobe
imposedlateritisdesignedintoit.

23. Software Quality Factors Management
▪Itisthedutyofeveryindividualinthesoftwaredevelopmentteamthatqualityis
maintainedevenbeforesomeformalqualityassuranceproceduresareapplied.This
practiceimprovesthequalityofallsoftwareproducedbytheorganization.
▪Applicationoftechnicalmethods,conductingformaltechnicalreviews(FTR),software
testing,controlofchange,measurementandrecordkeepingandreportingarethe
activitiesinvolvedinSQA.

24. Software Quality Factors Role in SQA
▪Asforsoftwaredevelopment,weknowthateveryprojectisdifferentandhasitsown
uniquecharacteristicsandchallenges.
▪Thereisnomagicrecipeisawell-knownfactwhenitcomestodevelopingsoftware
projectsorqualityassuranceprocesses.However,therearekeyelementstoconsider
thatcanensuregradeAqualityassurance:
1.KnowtheBusinessLogic:Therearedifferentroleswithinasoftwareproject,suchasthe
ProductOwner.Itisverycommonforthispersontohavealltheinformationregardingthe
product.Ingeneralterms,theProductOwneronlysharesinformationdirectlyrelatedtothe
partoftheprojectthatisgoingtobedeveloped.

25. Software Quality Factors Role in SQA
2.KnowtheProgrammingLanguage:Thereisaprogramminglanguageforeveryneed,
beitformobile,desktop,orwebapps.Thoughitisalmostimpossibletoknowall
programminglanguages,itisessentialtohaveknowledgeofthosethatapplytoprojects
thataqualityengineerwillbeworkingon.
3.LettheQualityEngineerTakeOwnership:AnimportantroleisplayedbytheProduct
Ownerineverysoftwareproject;however,itisimportantforthequalityengineertotake
ownershipoftheprojectasthiscontributestoeffectivedecisionmaking.
4.LettheQualityEngineerProvideSolutions:Fromtheverybeginningofsoftwarequality
assurance,itwasunderstoodthataqualityengineer’smaintaskwastoreporterrors.Yet
thisisonlyoneoftheirmultipletasks.

26. Any Questions?

27. Thank You!

28. Software Testing &
Quality Assurance

29. Components of Software Quality Assurance
Unit No. 2

30. Components of the Software Quality Assurance System

31. Objectives
After completing this session, you will be able to:
▪Define the Components of Software Assurance System.
▪Define the Contract Review of Software Quality Assurance.
▪Explain the Development & Quality Plans.

32. Components of Software Quality Assurance
▪Pre-project Components
▪Project Life Cycle Activities Assessment Components
▪ Components of Infrastructure Error Prevention and Improvement
▪Software Quality Management Component
▪ Standardization, Certification, and SQA System Assessment Components
▪The Human Components
5

33. Pre-project Components:
▪Consideringtheresourcesrequired,thescheduleandbudgetthisassuresthatthe
projectcommitmentshavebeenclearlydefinedandthedevelopmentandqualityplans
havebeencorrectlydetermined.

34. Project Life Cycle Activities Assessment Components
▪Thedevelopmentlifecycleandtheoperation–maintenancearethetwostagesofthe
projectlifecycle:
▪Thedetectionofdesignandprogrammingerrorsiscarriedoutbythecomponentsofthe
developmentlifecyclestage.
▪Reviews,ExpertopinionsandSoftwaretestingarethesub-classesinwhichthese
componentsaredividedinto.
▪AppliedmainlyforfunctionalitytoimprovethemaintenancetaskstheSQAcomponents
usedduringtheoperation–maintenancephaseincludesspecializedmaintenance
componentsaswellasdevelopmentlifecyclecomponents.

35. Components of Infrastructure Error Prevention and Improvement
▪Theobjectiveofthesecomponents,whichisappliedthroughouttheentireorganization,
istoeliminateoratleastreducetherateoferrors,basedontheorganization’s
accumulatedSQAexperience:
1.Softwarequalitymanagementcomponents
2.Standardization,CertificationandSQAsystemassessmentcomponents
3.OrganizingforSQA–thehumancomponent

36. Software Quality Management Component
▪ThemanagerialSQAcomponentssupportthemanagerialcontrolofsoftware
developmentprojectsandmaintenanceservices.Thecontrolcomponentsinclude
Projectprogresscontrol,Softwarequalitymetrics,Softwarequalitycosts:
1.Project Progress Control
2.Software Quality Metrics
3.Software Quality Costs

37. Standardization, Certification, and SQA System Assessment
Components
▪Theobjectiveistoutilizeinternationalprofessionalknowledge,professionalevaluation
andmeasurementoftheorganization’sSQAachievement.Classifiedintotwosub-
classesarethestandardsavailable:QualitymanagementstandardsandProjectprocess
standards:
1.Quality Management Standards
2.Project Process Standards

38. The Human Components
▪TheindividualsrelatedwithSQAareputtogetherinthisphasewhoincludesupervisors,
tryingstaff,SQAtrustees,SQApanelindividuals,andSQAgatheringpeople.Separately
eachofthemaddstostartandsupporttheexecutionofSQAparts,distinguish
deviationsfromSQAstrategyandapproach,andproposeupgrades.
▪Softwareprojectsdevelopedbysoftwarehousesfortheuseofothercompaniesare
usuallyknownasexternalprojectsoroutside-contractedprojects.Usuallycharacterized
bystrong/tightcustomer-supplierrelationship.
▪Softwareprojectsdevelopedbyoneunitofanorganizationtoanotherunitinthesame
organizationisusuallyknownasinternalprojectorin-houseprojectsusually
characterizedbyweak/loosecustomer-supplierrelationship.

39. Contract Review
▪Contractsarevitallyimportant.Whendeliveredsoftwaredoesnotperformasexpected
theyarethebasisforlitigation.
▪Thebadcontractsariseoutofpoorlydefinedrequirementsandunrealisticbudgetsand
schedules.
▪Theresultispoorqualitysoftware.PreventiveQualityAssurancestartswithadiscussion
ofContracts.
▪Acontractreviewisacontractualprocessusedtoidentifyandanalyzethekeyprovisions
withinanagreement.
▪Alegalprofessionalwillreadeachcontractthoroughlytounderstandthetermsand
conditionsandhighlightrisksorrelevantinformation.

40. Contract Review Cont ..
▪Thesoftwarequalityelementthatreducestheprobabilityofsuchundesirablesituations
isContractReviewwhichistheSQAcomponentdevisedtoguidereviewdraftsof
proposalandcontractdocuments.
1.Reviewfinalproposaldraftandcustomer’srequirementdocumentsandexplanationsof
requirements,costs,resources,maybewithpartners/subcontractorsbyreviewingthe
proposeddraftpriortosubmissiontopotentialcustomer.
2.Reviewdraftonthebasisoftheproposalandunderstandingsreachedduringthe
contractnegotiationsessionsbyreviewingthecontractpriortosigning.Majoractivities
andelaboratechecklistsareoftenused.

41. Contract Draft Review Objectives
▪Inthecontractdraftnounclarifiedissuesremain.
▪Correctlydocumentedareallunderstandingsreachedsubsequenttotheproposal.
▪No“new”changes,additions,oromissionsthathavenotbeenfullydiscussedhave
enteredthecontractdraft.

42. Development and Quality Plans
▪Thedevelopmentandqualityplanobjectivesareschedulingdevelopmentactivitiesthat
willleadtothesuccessfulandtimelycompletionoftheproject,recruitingteammembers
andallocatingdevelopmentresources,resolvingdevelopmentrisks,implementing
requiredSQAactivities,providingmanagementwithdataneededforprojectcontrol.
▪Specifyingthequalitystandards,practices,resources,specificationsandthesequence
ofactivitiesrelevanttoaparticularproduct,service,project,orcontractisadocument,
orseveraldocumentsthatisaqualityplan.

43. Quality Plans should Define
▪Theobjectivestobeattainedsuchascharacteristicsorspecifications,uniformity,
effectiveness,aesthetics,cycletime,cost,naturalresources,utilization,yieldand
dependability.
▪Theoperatingpracticeorproceduresoftheorganizationconstitutethestepsinthe
processes.
▪Duringthedifferentphasesoftheprocessorprojectallocationofresponsibilities,
authorityandresources.
▪Specificdocumentedstandards,practices,proceduresandinstructionstobeapplied.

44. Quality Plans should Define Cont ..
▪Atappropriatestagessuitabletesting,inspection,examination,andauditprograms.
▪Asaprocessisimprovedadocumentedprocedureforchangesandmodificationstoa
qualityplan.
▪Amethodformeasuringtheachievementofthequalityobjectives.
▪Otheractionsnecessarytomeettheobjectives.

45. Quality Plans should Define Cont ..
▪Atthehighestlevel,qualitygoalsandplansshouldbeintegratedwithoverallstrategicplansof
theorganization.
▪Atlowerlevels,thequalityplanassumestheroleofanactionableplan.Suchplansmaytake
manydifferentformsdependingontheoutcometheyaretoproduce.
Intheprojectdevelopmentplanthemainissuestreatedare:
▪Schedules
▪Manpowerandhardwareresourcesrequired
▪Riskevaluations
▪Teammembers,subcontractorsandpartnershipsareorganizationalissues
▪Projectmethodology,developmenttools,etc.
▪Softwarereuseplans

46. Quality Plans should Define Cont ..
In the project’s quality plan,the main issues treated are:
▪Qualitygoals,expressedintheappropriatemeasurableterms.
▪Criteriaforstartingandendingeachprojectstage.
▪Listsofreviews,tests,andotherscheduledverificationandvalidationactivities.

47. Elements of the Development Plan
Projectproductsordeliverables:
Designdocumentsspecifyingdatesofcompletionofsoftwareproducts(specifying
completiondateandinstallationsite),trainingtasks(specifyingdates,participantsandsites),
interfaceswithexistingsoftwarepackages,interfaceswithothersoftwareand/orhardware
developmentteams(cooperationandcoordinationlinks),interfaceswithexistinghardware.
1.Project Staff Organization
2.Control Methods

48. Elements of the Quality Plan
▪Quality goals refer to the developed software system’s substantive quality requirements.
- Planned Review Activities.
-Planned Software Tests.

49. Elements of Development and Quality Plans
Elements of Development and Quality Plans for your Projects are:
▪Thedevelopmentplanshouldincludeprojectproductsindicating“deliverables”,project
benchmarks/standards,developmentrisks,estimatesofprojectcosts.
▪Thequalityplanshouldincludethequalitygoals.

50. Any Questions?

51. Thank You!

52. Software Testing &
Quality Assurance

53. SQA Components in the Project Life Cycle
Unit No. 3

54. Objectives
After completing this unit, you will be able to:
▪Define the Components of Software Assurance System.
▪Define Software Testing.
▪Explain the Integrating Quality Activities in the Project Life
Cycle.

55. Introduction
▪IntegratingthequalityactivitiesintheprojectlifecycleareincludedinSQAcomponents.
Itscomponentsarereview,expertopinions,softwaretesting,softwaremaintenanceand
assuringthequalityofexternalparticipant’scontributions.
▪Thecomponentslikereviews,expertopinionsandfindingdefectsinsoftwaredesignand
programmingareincludedinitandinthesoftwaremaintenancelifecycleitincludes
specializinginmaintenancecomponentsanddevelopmentlifecyclecomponentsfor
enhancingmaintenancetasks.

56. Introduction Cont ..
▪SQA Components in the Project Life Cycle and Strategies.
▪Integrating Quality Activities in the Project Life Cycle.
▪Reviews
▪Software Testing –Strategies.
5

57. Introduction Cont ..
The two stages that comprise the project life cycle are:
1.Thedesignandprogrammingerrorsaredetectedinthedevelopmentlifecyclestage.
Reviews,Expertopinions,Softwaretesting,Assuranceofthequalityofthesub-
contractor’sworkandcustomersuppliedpartsareitscomponents.
2.Specializedmaintenancecomponentsaswellasdevelopmentlifecyclecomponents,
whichareappliedmainlyforfunctionalityimprovingmaintenancetasksareincludedin
theoperation-maintenancestage.

58. SQA Components in The Project Life Cycle
▪AimedatensuringqualityinsoftwareengineeringprocessesasetofactivitiesisSQAwhich
guaranteesthatthedevelopedsoftwaremeetsandconformsthedefinedorstandardized
qualityspecifications.
▪Anongoingprocesswithinthesoftwaredevelopmentlifecycle,itroutinelychecksthe
developedsoftwaretoconfirmthatitmeetsthedesiredqualitymeasures.
▪TotestthesoftwareSQAincorporatesandimplementssoftwaretestingmethodologies.Until
thesoftwareiscomplete,SQAprocessestestforqualityineachphaseofdevelopment.
▪Thesoftwaredevelopmentprocessmovesintothenextphaseonlyoncethecurrentphase
complieswiththerequiredqualitystandards.Itworkswithindustrystandardsthathelpin
buildingsoftwarequalityguidelinesandimplementationstrategies.

59. SQA Components in The Project Life Cycle Cont ..
A.Integrating Quality Activities in the Project Life Cycle
Testing within a life cycle model.
The characteristics of good testing include:
▪Thereisacorrespondingtestingactivityforeverydevelopmentactivity.
▪Foragiventestleveltheanalysisanddesignoftestsshouldbeginduringthe
correspondingdevelopmentactivity.
▪Inreviewingdocumentsassoonasdraftsareavailableinthedevelopmentcycletesters
shouldbeinvolved.

60. SQA Components in The Project Life Cycle Cont ..
B.Review
A process or meeting of project personnel, managers, users, customers or other interested parties for their
comment or approval during which a work product or set of work products is presented.
The objectives of Review are:
Direct Objectives:
▪Detectionofanalysisanddesignerrors.
▪Identificationofnewrisksthatarelikelytoaffectcompletionoftheproject.
▪Identificationofdeviationsfromtemplatesandstyleprocedures.
▪Approvaltobeprovidedfortheanalysisordesignproduct.
Indirect Objectives:
▪Forexchangeofprofessionalknowledge.
▪Recordingtheanalysisanddesignerrorsthatwillserveasabasisforfuturecorrectiveactions.

61. SQA Components in The Project Life Cycle Cont ..
Types of Reviews:
1. Walkthrough Review
▪Forevaluationorinformationalpurpose,itisaninformalmeeting.
▪Theauthorleadsittoagroupofcolleagues,theauthordescribeshisworkproductand
comments.
2.Technical Review/Peer Review
▪Thefocusisonachievingconsensusaboutthetechnicalcontentofadocumentina
discussionmeeting.
▪Peerandtechnicalexperts(e.g.,architects,chiefdesigners,andkeyusers)areincluded,
nomanagementparticipation.

62. SQA Components in The Project Life Cycle Cont ..
Types of Reviews Cont ..:
3. Inspection
▪Themostformalreviewtypethatisprescribedandsystematicwheretherolesarewell-
defined(moderator,reader,andarecorder).
▪Atrainedmoderator(notauthor)usuallyleadsit.
▪Attendeesshouldprepareforthistypeofmeetingbyreadingthroughthedocument.
▪Alogginglistisusedtodocumentthedefectsfound.
▪Theresultoftheinspectionmeetingshouldbeawrittenreport.
▪Themetricsaregatheredandanalyzedtooptimizetheprocess.

63. SQA Components in The Project Life Cycle Cont ..
C. Software Testing
▪Softwaretestingdeterminesthecorrectness,completenessandqualityofsoftwarebeing
developed.
▪Testingisdefinedas“theprocessofevaluatingasystemorsystemcomponentbymanualor
automatedmeanstoverifythatitsatisfiesspecifiedrequirementsortoidentifydifferences
betweenexpectedandactualresults”.
▪Softwaretestingisrelatedtoverificationandvalidation.Theprocessofensuringthatthe
softwareisdevelopedaccordingtoitsspecificationsisreferredtobyverificationwhichuses
techniqueslikereviews,analysis,inspectionsandwalkthroughs.
▪Verification:Isthesoftwarebeingdevelopedintherightway?
▪Validation:Istherightsoftwarebeingdeveloped?

64. SQA Components in The Project Life Cycle Cont ..
Software Testing Cont ..
To make sure that the software is functioning in accordance with the user requirements,
software testing is performed either manually or by using automated tools. Various
advantages associated with testing are listed below:
▪Removingerrorsthatpreventsoftwarefromproducingoutputsaccordingtouser
requirements.
▪Removingerrorsthatleadtosoftwarefailure.
▪Ensuringthatthesoftwareconformstobusinessaswellasuser’sneeds.
▪Ensuringthatthesoftwareisdevelopedaccordingtouserrequirements.
▪Improvingthequalityofthesoftwarebyremovingallpossibleerrorsfromit.

65. SQA Components in The Project Life Cycle Cont ..
▪Softwaretestingisaimedatidentifyinganybugs,errors,faults,orfailures(ifany)presentin
thesoftware.Errorscanbepresentinthesoftwareonaccountofthefollowingreasons:
▪Programmingerrors:Programmerscanmakemistakeswhiledevelopingthesourcecode.
UnclearRequirements:Theuserisnotclearaboutthedesiredrequirements,orthe
developersareunabletounderstandtheuserrequirementsinaclearandconcisemanner.
SoftwareComplexity:Thegreaterthecomplexityofthesoftware,themorethescopeof
committinganerror(especiallybyaninexperienceddeveloper).
ChangingRequirements:Theusersusuallykeeponchangingtheirrequirements,andit
becomesdifficulttohandlesuchchangesinthelaterstageofdevelopmentprocess.Therefore,
therearechancesofmakingmistakeswhileincorporatingthesechangesinthesoftware.

66. SQA Components in The Project Life Cycle Cont ..
TimePressures:Maintainingscheduleofsoftwareprojectsisdifficult.Whendeadlinesare
notmet,theattempttospeeduptheworkcauseserrors.
PoorlyDocumentedCode:Ifthecodeisnotwelldocumentedorwellwritten,then
maintainingandmodifyingitbecomesdifficult.Thiscauseserrorstooccur.

67. SQA Components in The Project Life Cycle Cont ..
The software testing objectives are:
▪Todetectdefects.
▪Todeterminethatthesoftwaresatisfiesspecifiedrequirements.
▪Todemonstratethatthesoftwareisfitforitspurpose.Thetestprocessstepsare
PlanningandControl,AnalysisandDesign,ImplementationandExecution,Reporting
andEvaluatingExitCriteria,TestClosureActivities.

68. SQA Components in The Project Life Cycle Cont ..
Test Planning and Control:
▪Thetestplanningandcontrolhasthefollowingmajortasks:
▪Determinethescope,risks,andthetestingobjectives.
▪Determinethetestapproach(techniques,testitems,coverage,identifyingandinterfacingwith
theteamsinvolvedintesting,testware).
▪Determinetherequiredtestresources(e.g.,people,testenvironment,PCs).
▪Scheduletestanalysisanddesigntasks,testimplementation,executionandevaluation.
▪Determinetheexitcriteriatoknowwhentestingisfinished.
▪Testcontrolisanongoingactivity.

69. SQA Components in The Project Life Cycle Cont ..
Test Planning and Control Cont ..
▪Monitorstatusandtakecorrectiveactionsifnecessary.
▪Testcontrolhasthetasks:Measureandanalyzetheresultsofreviewsandtesting,
monitoranddocumentprogress,testcoverageandexitcriteria,provideinformationon
testing,initiatecorrectiveactions,makedecisions:Tocontinuetesting,tostoptesting,to
releasethesoftwareortoretainitforfurtherwork.

70. Software Testing Strategies
TestStrategy
▪AteststrategyisaplanfordefininganapproachtotheSoftwareTestingLifeCycle(STLC).In
addition,theteststrategyprovidesthefollowingdetails,whicharerequiredwhilewritingthe
testdocument:
➢Whattechniquemustbeusedinadditiontothis?
➢Whichofthemoduleswillbeexamined?
➢Whatcriteriaapplyforentryandexit?
➢Whatkindoftestingisnecessary?
▪Softwaretestingistheprocessofevaluatingasoftwareapplicationtoidentifyifitmeets
specifiedrequirementsandtoidentifyanydefects.Thefollowingarecommontesting
strategies:

71. Types of Strategies
▪Blackboxtesting–Teststhefunctionalityofthesoftwarewithoutlookingattheinternal
codestructure.
▪Whiteboxtesting–Teststheinternalcodestructureandlogicofthesoftware.
▪Unittesting–Testsindividualunitsorcomponentsofthesoftwaretoensuretheyare
functioningasintended.
▪Integrationtesting–Teststheintegrationofdifferentcomponentsofthesoftwareto
ensuretheyworktogetherasasystem.
▪Functionaltesting–Teststhefunctionalrequirementsofthesoftwaretoensuretheyare
met.

72. Types of Strategies Cont ..
▪Systemtesting–Teststhecompletesoftwaresystemtoensureitmeetsthespecified
requirements.
▪Acceptancetesting–Teststhesoftwaretoensureitmeetsthecustomer’sorend-user’s
expectations.
▪Regressiontesting–Teststhesoftwareafterchangesormodificationshavebeenmade
toensurethechangeshavenotintroducednewdefects.
▪Performancetesting–Teststhesoftwaretodetermineitsperformancecharacteristics
suchasspeed,scalability,andstability.
▪Securitytesting–Teststhesoftwaretoidentifyvulnerabilitiesandensureitmeets
securityrequirements.

73. Software Testing Objectives
▪Theprocessofinvestigatingandcheckingaprogramtofindwhetherthereisanerroror
notanddoesitfulfilltherequirementsornotiscalledtesting.
▪Whenthenumberoferrorsfoundduringthetestingishigh,itindicatesthatthetesting
wasgoodandisasignofgoodtestcase.
▪Findinganunknownerrorthatwasn’tdiscoveredyetisasignofasuccessfulandagood
testcase.
▪Themainobjectiveofsoftwaretestingistodesignthetestsinsuchawaythatit
systematicallyfindsdifferenttypesoferrorswithouttakingmuchtimeandeffortsothat
lesstimeisrequiredforthedevelopmentofthesoftware.

74. Advantages of Software Testing
▪Improvessoftwarequalityandreliability.
▪Enhances user experience.
▪Increases confidence.
▪Facilitates maintenance.
▪Reduces costs.

75. Disadvantages of Software Testing
▪Time-consuming.
▪Testingrequiresspecializedskillsandresources,whichcanbeexpensive.
▪Unpredictable results.
▪Delays in delivery.

76. Any Questions?

77. Thank You!