Types and levels of testing chpter 2 (1).pdf

Types and level of testing which is a Ste topic

1. Unit 2 Marks 18
Types and levels of testing

2. 2.1 Levels of testing
Ingeneral,therearefourlevelsof
testing: unittesting,integration
testing,systemtesting,andacceptance
testing.ThepurposeofLevelsoftestingisto
makesoftwaretestingsystematicandeasily
identifyallpossibletestcasesataparticular
level.

3. 2.2 unit testing
•Unit testing focuses verification effort on the
smallest unit of software design—the
software component or module. Using the
component-level design description as a
guide, important control paths are tested to
uncover errors within the boundary of the
module.

4. Video lecture on
•Unit testing:

5. Therelativecomplexityoftestsandtheerrors
thosetestsuncoverislimitedbythe
constrainedscopeestablishedforunittesting.
Theunittestfocusesontheinternal
processinglogicanddatastructureswithinthe
boundariesofacomponent.Thistypeof
testingcanbeconductedinparallelfor
multiplecomponents.

6. Stubs and drivers
Thesedummypiecesofcodearethestubs.
Ontheotherhand,Driversaretheones,
whicharethe"calling"programs.Driversare
used in bottom up testing
approach.Driversaredummycode,whichis
usedwhenthesubmodulesarereadybutthe
mainmoduleisstillnotready....Thisdummy
codeisthencalledDriver.

8. 2.2 Integration testing
Integrationtestingisasystematictechniquefor
constructingthesoftwarearchitecturewhileat
thesametimeconductingteststouncovererrors
associatedwithinterfacing.
Correctionisdifficultbecauseisolationofcauses
iscomplicatedbythevastexpanseoftheentire
program.
Onceallthecomponentsormodulesareworking
independently,thenweneedtocheckthedata
flowbetweenthedependentmodulesisknown
asintegrationtesting.

10. •Integration testing
•Integration testing is the second level of the software
testing process comes after unit testing. In this testing,
units or individual components of the software are
tested in a group. The focus of the integration testing
level is to expose defects at the time of interaction
between integrated components or units.
•Unit testinguses modules for testing purpose, and
these modules are combined and tested in integration
testing. The Software is developed with a number of
software modules that are coded by different coders or
programmers. The goal of integration testing is to check
the correctness of communication among all the
modules.

11. Video lecture on
•Integration testing:

12. Top down integration
Top-downintegrationtestingisanincremental
approachtoconstructionofthesoftware
architecture.Modulesareintegratedby
movingdownwardthroughthecontrol
hierarchy,beginningwiththemaincontrol
moduleTop-downintegration.(mainprogram).

14. Bottom-up integration
Bottom-upintegrationtesting,asitsname
implies,beginsconstructionandtestingwith
atomicmodules(i.e.,componentsatthe
lowestlevelsintheprogramstructure).
Becausecomponentsareintegratedfromthe
bottomup,thefunctionalityprovidedby
componentssubordinatetoagivenlevelis
alwaysavailableandtheneedforstubsis
eliminated.

16. Bi-directional testing
There are 2 types of Integration Testing
1) Incremental Integration Testing
2) Non-Incremental Integration Testing.

17. Afterunittestingiscompleted,developer
performsintegrationtesting.Itistheprocess
ofverifyingtheinterfacesandinteraction
betweenmodules.Whileintegrating,there
arelotsoftechniquesusedbydevelopersand
oneofthemistheincrementalapproach.

18. IncrementalTestingMethodologies
TopdownIntegration-Thistypeofintegrationtestingtakesplacefrom
toptobottom.UnavailableComponentsorsystemsaresubstitutedby
stubs.
BottomUpIntegration-Thistypeofintegrationtestingtakesplacefrom
bottomtotop.UnavailableComponentsorsystemsaresubstitutedby
Drivers.
Functionalincremental-TheIntegrationandtestingtakesplaceonthe
basisofthefunctionsorfunctionalitiesasperthefunctionalspecification
document.

19. Non–incrementalintegration
Thereareoftenatendencytoattemptnon-
incrementalintegration.Innon-incremental
integrationallcomponentsarecombined.The
entiresoftwareprogramsaretestedasawhole.It
usuallyresultsintoasetoferrors.Theseerrors
areverydifficulttoisolatebecauseoflargesizeof
program(duetobigbang).Oncetheseerrorsare
correctednewonesappearandthisprocess
continueslikeaendlessloop.

20. Video lecture on
•Software testingSTLC:

21. 2.3 Testing on web application
Webapplicationisabitdifferentandcomplex
totestastesterdon’thavethatmuchcontrol
overtheapplication.Applicationisloadedon
theserverwhoselocationmayormaynotbe
knownandnoexeisinstalledontheclient
machine,youhavetotestitondifferentweb
browsers

22. Video lecture on
•Web –Applicationtesting :

23. Webapplicationsaresupposedtobetested
ondifferentbrowsersandOSplatformsso
broadlyWebapplicationistestedmainlyfor
browsercompatibilityandoperatingsystem
compatibility,errorhandling,staticpages,
backendtestingandloadtesting.

24. Theapplicationsaccessibleinbrowserwould
bedevelopedinHTML,DHTML,XML,
JavaScriptetc.(Wecanmonitorthroughthese
applications)Applicationsforthewebserver
wouldbedevelopedinJava,ASP,JSP,VBScript,
JavaScript,Perl,ColdFusion,PHPetc.(Allthe
manipulationsaredoneonthewebserver
withthehelpoftheseprogramsdeveloped)

25. Load testing
Loadtestingisasoftwaretestingtechnique
usedtoexaminethebehaviorofasystem
whensubjecttobothnormalandextreme
expectedloadconditions.Loadtestingis
generallyperformedundercontrolled
laboratoryconditionsinordertodistinguish
betweentwodifferentsystems

26. Stress testing
Stresstestingreferstothetestingofsoftware
orhardwaretodeterminewhetherits
performanceissatisfactoryunderanyextreme
andunfavorableconditions,whichmayoccur
asaresultofheavynetworktraffic,process
loading,underclocking,overclocking(process)
andmaximumrequestsforresource
utilization.

27. Security testing
SECURITYTESTINGisatypeof
softwaretestingthatintendstouncover
vulnerabilitiesofthesystemanddetermine
thatitsdataandresourcesareprotectedfrom
possibleintruders.

28. Client server testing
Inclientserverapplicationyouhavetwo
differentcomponentstotest.Applicationis
loadedonservermachinewhilethe
applicationexeoneveryclientmachine.You
willtestbroadlyincategorieslike,GUIonboth
sides,functionality,Load,client-server
interaction,backend.Thisenvironmentis
mostlyusedinIntranetnetworks.Youare
awareofnumberofclientsandserversand
theirlocationsinthetestscenario

29. •Thistypeoftestingusuallydonefor2tier
applications(usuallydevelopedforLAN)Here
wewillbehavingfront-endandbackend.The
applicationlaunchedonfront-endwillbe
havingformsandreportswhichwillbe
monitoringandmanipulatingdata

30. Video lecture on
•FunctionalTesting :

31. 2.4 Acceptance testing
Acceptancetesting,atestingtechnique
performedtodeterminewhetherornotthe
softwaresystemhasmettherequirement
specifications.Themainpurposeofthistestis
toevaluatethesystem'scompliancewiththe
businessrequirementsandverifyifitishas
mettherequiredcriteriafordeliverytoend
users.

33. functional test case for amount
transfer module

35. writing a test case for the ICICI application’s Login
module:

36. Alpha ,beta testing
Alphatestingisatypeofacceptancetesting;
performedtoidentifyallpossibleissues/bugsbefore
releasingtheproducttoeverydayusersorpublic.The
focusofthistestingistosimulaterealusersbyusing
blackboxandwhiteboxtechniques.Theaimistocarry
outthetasksthatatypicalusermightperform.Alpha
testingiscarriedoutinalabenvironmentandusually
thetestersareinternalemployeesoftheorganization.
Toputitassimpleaspossible,thiskindoftestingis
calledalphaonlybecauseitisdoneearlyon,nearthe
endofthedevelopmentofthesoftware,andbefore
betatesting.

37. Beta Testing of a product is performed by "real
users" of the software application in a "real
environment" and can be considered as a form of
external user acceptance testing.
Beta version of the software is released to a
limited number of end-users of the product to
obtain feedback on the product quality. Beta
testing reduces product failure risks and provides
increased quality of the product through
customer validation.

38. GUI testing
SuccessofanyGUIapplicationdependson
howitinteractswithuserthroughitsuser
interface,howtheuseractionsareperformed
toaccessapplication'sfeaturesandwhether
applicationrespondsinfunctionallycorrect
manner.Anapplicationwithincorrect
behaviourorinvaliduserinteractioncanlead
tohugeproblems.Wewilltrytounderstand
fewimportantaspectswithGUITesting.

39. Video lecture on
•Regressiontesting :

40. Bloom Level 2 marks
question(Knowledge, Remember)
DefineUnittesting.
WhatisAcceptanceTesting.
StatethePerformanceTesting.
Definestresstesting.
Statetheregressiontesting.

41. Understand, Apply level 4 marks
Question
•Difference between alpha and beta testing .
•Explain Incremental and Non-Incremental.
•Explain Recovery Testing and Security Testing.
•Explain in detail client-server testing.
•Describe in detail GUI testing
•Explain Bi-Directional integration

42. Software Engineering Unit 1
•Objective Questionpart 1

43. Question bank
ExplainUnittesting?
ExplainTop-Downintegration?
ExplainBottom-Upintegration?
ExplainIncrementalandNon-Incremental?
ExplainBi-Directionalintegration?
ExplainDecompositionBasedIntegration?
ExplainRecoveryTestingandSecurityTesting?
ExplainPerformanceTesting?

44. ExplainUnittestingindetail?
Explainintegrationindetail?
ExplainTop-DownIntegration?
ExplainBottom-UpIntegration?
ExplainAcceptanceTesting?

45. WhatisUnittesting?Explainitindetail?
WhatisIntegrationtesting?Explainitin
details?
WhatisSystemtesting?Explainitindetails?
WhatisAcceptancetesting?Explainitin
details?

46. Question and answer
DefineUnitTestandcharacterizedtheunittest.
Ataunittestasinglecomponentistested.Aunitisthe
smallestpossibletestable
softwarecomponent.
Itcanbecharacterizedinseveralways
Aunitinatypicalprocedureorientedsoftware
systems.
Itperformsasinglecohensivefunction.
Itcanbecompiledseparately.
Itcontainscodethatcanfitonasinglepageora
screen.

47. •DefineintegrationTest.
•Attheintegrationlevelseveralcomponentsaretested
asagroupandthetester
•investigatescomponentinteractions.
•.DefineSystemtest.
•Whenintegrationtestarecompletedasoftware
systemhasbeenassembledandits
•majorsubsystemshavebeentested.Atthispointthe
developers/testersbegintotestit
•asawhole.Systemtestplanningshouldbeginatthe
requirementsphase

48. DefineAlphaandBetaTest.
Alphatestdeveloper’stousethesoftwareand
notetheproblems.
Betatestwhouseitunderrealworld
conditionsandreportthedefecttothe
Developingorganization

49. •Define functional Testing.
•Functional tests at the system level are used ensure that the
behavior of the system
•adheres to the requirement specifications.
•What are the two major requirements in the Performance testing.
•Functional Requirement: User describe what functions the
software should
•perform. We test for compliance of the requirement at the system
level with the
•functional based system test.
•Quality Requirement: They are nonfunctional in nature but
describe quality
•levels expected for the software

50. •What are the steps for top down integration?
•Main control module is used as a test driver and stubs
are substituted for all
•components directly subordinate to the main module.
•Depending on integration approach (Depth or breadth
first) subordinate stubs are
•replaced one at a time with actual components.
•Tests are conducted as each component is integrated.
•The completion of each set of tests another stub is
replaced with real component

51. •What is meant by regression testing?
•Regression testing is used to check for defects
propagated to other modules by
•changes made to existing program. Thus,
regression testing is used to reduce the side
•effects of the changes.

52. ListtheTestplancomponents.
Testplanidentifier
Introduction
Itemstobetested
Featurestobetested
Approach
Pass/failcriteria
Suspensionandresumptioncriteria

53. Testdeliverables
TestingTasks
Testenvironment
Responsibilities
Staffingandtrainingneeds
Scheduling
Risksandcontingencies
Testingcosts
Approvals.

54. •Advantages of Black Box Testing
•The test is unbiased because the designer and the tester are independent
of each other.
•The tester does not need knowledge of any specific programming
languages.
•The test is done from the point of view of the user, not the designer.
•Test cases can be designed as soon as the specifications are complete.
•Disadvantages of Black Box Testing
•The test can be redundant if the software designer has already run a test
case.
•The test cases are difficult to design.
•Testing every possible input stream is unrealistic because it would take a
inordinate amount of time; therefore, many program paths will go
untested.