Domov technika Integration Testing

Integration Testing



Introduction

Integrationtesting(alsocalledassemblytesting,jointtesting)isalogicalextensionofunittesting.Itssimplestformis:Combinetwotestedunitsintoonecomponentandtesttheinterfacebetweenthem.Inthissense,componentsrefertotheintegrationofmultipleunits.Inarealsolution,manyunitsarecombinedintocomponents,andthesecomponentsareaggregatedintoalargerpartoftheprogram.Themethodistotestthecombinationoffragmentsandfinallyexpandintoaprocess,testingthemodulestogetherwithothergroupsofmodules.Finally,allthemodulesthatmakeuptheprocessaretestedtogether.Inaddition,iftheprogramconsistsofmultipleprocesses,youshouldtesttheminpairsinsteadoftestingallprocessesatthesametime.

Theproblemsthatarisewhentheintegrationtestteststhecombinedunit.Byusingatestplanthatrequirestestingeachunitbeforecombiningtheunitsandensuringtheviabilityofeachunit,youcanknowthatanyerrorsfoundwhencombiningtheunitsarelikelytoberelatedtotheinterfacesbetweentheunits.Thismethodreducesthenumberofpossiblesituationstoasimplerlevelofanalysis.Aneffectiveintegrationtesthelpstosolvethecompatibilityandoperabilityproblemsofrelatedsoftwarewithothersystems.

Integrationtestingisbasedonunittesting.Ittestswhetherallthesoftwareunitsareassembledintomodules,subsystemsorsystemsinaccordancewiththerequirementsoftheoutlinedesignspecifications.Technicalindicatorsandrequiredactivities.Inotherwords,beforetheintegrationtest,theunittestshouldhavebeencompleted,andtheobjectusedintheintegrationtestshouldbethesoftwareunitthathasbeenunittested.Thisisveryimportant,becauseiftheunittestisnotpassed,theeffectoftheintegrationtestwillbegreatlyaffected,andthecostofthesoftwareunitcodeerrorcorrectionwillbegreatlyincreased.

Integrationtestingisalogicalextensionofunittesting.Intheactualsolution,integrationreferstotheaggregationofmultipleunits,manyunitsarecombinedintomodules,andthesemodulesareaggregatedintoalargerpartoftheprogram,suchassub-systemsorsystems.Themethodusedinintegrationtestingistotestwhetherthecombinationofsoftwareunitscanworknormallyandwhetheritcanbeintegratedwithothergroupsofmodulestowork.Finally,itisnecessarytotestwhetherallthemodulecombinationsthatmakeupthesystemcanworknormally.Themainstandardheldbytheintegrationtestisthe"SoftwareOutlineDesignSpecification",andanyprogrammodulebehaviorthatdoesnotconformtothedescriptionshouldberecordedandreported.

Allsoftwareprojectscannotgetridofthisstageofsystemintegration.Nomatterwhatdevelopmentmodelisadopted,thespecificdevelopmentworkmuststartwithonesoftwareunit,andonlythroughintegrationcanthesoftwareunitformanorganicwhole.Thespecificintegrationprocessmaybeexplicitorimplicit.Aslongasthereisintegration,therewillalwaysbesomecommonproblems.Inengineeringpractice,thereisalmostnoproblemintheassemblyprocessofsoftwareunits.ItcanbeseenfromFigure1thatintegrationtestingtakesfarmoretimethanunittesting,anditisextremelyimpropertodirectlytransitionfromunittestingtosystemtesting.

Goal

Thegoalofintegrationtestingistousethosecomponentsthatpassunitteststoconstructtheprogramstructureinaccordancewiththedesignrequirements.Asinglemodulehashighqualitybutnotenoughtoguaranteethequalityoftheentiresystem.Manyhiddenfailuresarecausedbyunexpectedinteractionsbetweenhigh-qualitymodules.Thefollowingtwotestingtechniquesareusedforintegrationtesting:

1)Functionaltesting.Useblackboxtestingtechnologytotesttheinterfacespecificationsofthetestedmodule.

2)Non-functionaltesting.Testtheperformanceorreliabilityofthemodule.

Inaddition,thenecessityofintegrationtestingliesinthefactthatsomemodulescanworkindividually,buttheycannotbeguaranteedtoworkproperlywhenconnected.Problemsthatcannotbereflectedinsomepartsoftheprogrammaybeexposedintheoverallsituationandaffecttherealizationoffunctions.Inaddition,insomedevelopmentmodels,suchasiterativedevelopment,designandimplementationarecarriedoutiteratively.Inthiscase,thesignificanceofintegrationtestingisthatitcanindirectlyverifythefeasibilityoftheoutlinedesign.

Integrationtestingistoensurethattheunitscanbecombinedtooperateinaccordancewiththeintendedintentionandtoensurethattheincrementalbehavioriscorrect.Whatittestsincludestheinterfacebetweentheunitsandtheintegratedfunctions.Useblackboxtestingmethodstotestintegratedfunctions.Andperformregressiontestingonthepreviousintegration.

Implementation

Integrationtestingisaformaltestingprocessthatmustbecarefullyplannedandcoordinatedwiththecompletiontimeofunittesting.Whenmakingatestplan,thefollowingfactorsshouldbeconsidered:

1.Whichsystemassemblymethodisusedfortheassemblytest;

2.Thesequenceofconnectingeachmoduleintheassemblytestprocess;

3.Whetherthemodulecodepreparationandtestprogressareconsistentwiththesequenceofassemblytest

4.Whetherspecialhardwareequipmentisrequiredduringthetestprocess;

SolveAftersolvingtheaboveproblems,youcanlistthepreparationandtestplanofeachmodule,andindicatethedatewhentheunittestofeachmoduleiscompleted,thedateofthefirstintegrationtest,thedatewhentheintegrationtestiscompleted,andtherequiredtestcasesandexpectationsTestResults.

Intheabsenceofhardwareequipmentrequiredforsoftwaretesting,checkwhetherthedeliverydateofthehardwareisconsistentwiththeintegrationtestplan.Forexample,ifthetestrequiresadigitizerandaplotter,thecorrespondingtestshouldbearrangedwhenthesedevicescanbeputintouse,andaperiodoftimeshouldbereservedfortheinstallationanddeliveryofthehardwaretoleavetimemargin.Inaddition,thepreparationofthesoftware(drivermodule,stubmodule,testcasegenerationprogram,etc.)requiredforthetestneedstobeconsideredinthetestplan.

Aftertheunittest,itisnecessarytoconductanintegrationtesttofindandeliminatetheabove-mentionedproblemsthatmayoccurinthemoduleconnection,andfinallyconstitutetherequiredsoftwaresubsystemorsystem.Forsubsystems,integrationtestingisalsocalledcomponenttesting.

Anyreasonableorganizationofintegrationtesting,thatis,thechoiceofhowtoassemblethemodulestoformarunnablesystem,directlyaffectstheformofmoduletestcases,thetypeoftesttoolsused,themodulenumber,andtheorderoftesting,Thecostofgeneratingtestcasesanddebugging.Generally,therearetwodifferentassemblymethods:one-timeassemblymethodandvalue-addedassemblymethod.

Completioncriteria

Howtodeterminethattheintegrationtestprocessiscompleted,youcancheckaccordingtothefollowingaspects:

1.ThetestplanhasbeensuccessfullyimplementedAllintegrationtests;

2,theerrorsfoundwerecorrected;

3,thetestresultspassedthereviewofthespecialteam.

Integrationtestingshouldbecarriedoutbyadedicatedtestingteam,whichiscomposedofexperiencedsystemdesignersandprogrammers.Theentiretestactivityshouldbecarriedoutinthepresenceofthereviewers.

Aftercompletingthescheduledassemblytestwork,thetestteamshouldberesponsibleforsortingoutandanalyzingthetestresults,andformingatestreport.Thetestreportshouldrecordtheactualtestresults,theproblemsfoundinthetest,themethodstosolvetheseproblems,andtheresultsofthetestagainafterthesolution.Inaddition,someissuesthatcannotberesolvedandneedtobepaidattentiontobymanagersanddevelopersshouldberaised,andtestreviewsandfinaldecisionsshouldbeprovidedtoprovidesuggestionsforhandling.

Content

Integrationtestingprocess

AccordingtoIEEEstandardintegrationtestingisdividedinto4phases:planningphase,designphase,implementationphase,andexecutionphase(implementationphase))

Planningstage

1)Aboutoneweekafterthecompletionofthedesignreviewandreviewofthetimeschedule

2)InputtherequirementsspecificationoutlinedesigndocumentproductDevelopmentPlanroadmap

3)Theentryconditionsummarydesigndocumenthaspassedthereview

4)Activitysteps1.Determinethetestobjectandtestscope2.EvaluatetheintegrationtesttobetestedThenumberanddifficultyoftheobjects,namelytheworkload3.Determinethedivisionofrolesandtasks4.Identifythetime,tasks,constraintsandotherconditionsofeachstageofthetest5.Considercertainriskanalysisandcontingencyplans6.ConsiderandprepareforintegrationtestingneedsTesttools,testequipment,environmentandotherresources7.Considerthestrengthanddepthofexternaltechnicalsupport,andrelatedtrainingarrangements8.Definetestcompletionstandards

5)OutputIntegrationtestplan

6)TheexportconditionsTheintegrationtestplanhaspassedthebaselinereviewoftheoutlinedesignphase

Designphase1)Timearrangementdetaileddesignphasebegins2)InputrequirementsspecificationsManualsummarydesignintegrationtestplan3)Entryconditionsummarydesignbaselinepassedreview4)Activitysteps1.Structureanalysisoftheobjectundertest2.Integrationtestmoduleanalysis3.Integrationtestinterfaceanalysis4.Integrationteststrategyanalysis5.Integrationtesttoolanalysis6.Analysisofintegrationtestenvironment7.Estimationandarrangementofintegrationtestworkload.5)Outputintegrationtestdesign(scheme)6.ExportconditionsTheintegrationtestdesignhaspassedthedetaileddesignbaselinereview.Realizationstage1)Timearrangementiscarriedoutafterthecodingstagestarts2)Inputrequirementsspecificationoutlinedesignintegrationtestplanintegrationtestdesign3)Entryconditiondetaileddesignstage4)Activitysteps:1.Integrationtestcasedesign2.Integrationtestcodedesign(Ifneeded)3.Integrationtestscript(ifneeded)4.Integrationtesttool(ifneeded)5)OutputintegrationtestcaseintegrationtestprocedureIntegrationtestcodeintegrationtestscriptIntegrationtesttool6)ExportconditiontestcaseandtestprocedurepassedCodingphasebaselinereview,executionphase1)Timearrangement,unittestingcanbestartedafterthecompletionofintegrationtesting2)inputrequirementsspecificationoutlinedesignintegrationtestplanintegrationhighlydesignedintegrationtestcasesintegrationtestproceduresintegrationtestcode(ifany)integrationTestscriptintegrationtesttooldetaileddesigncodeunittestreport3)Entryconditionunitteststagehaspassedbaselinereview4)Activitystepexecutionintegrationtestcaseregressionintegrationtestcasewritingintegrationtestreport5)outputintegrationtestreport6)exitconditionintegrationThetestreporthaspassedthebaselinereviewoftheintegrationteststage

Workcontent

Requirementsacquisition

Thetestcontentoftheintegratedworkingversion,thatis,thespecificobjectofthetest.Integrationtestrequirementsmainlycomefromthedesignmodel(DesignModel)andintegrationcomponentplan(IntegrationBuildPlan).Integrationtestingfocusesonthebehavioroftheexternalinterfaceoftheintegratedversion.Therefore,thetestrequirementsmustbeobservableandmeasurable.

1.Theintegratedworkingversionshouldanalyzeitsclasscollaborationandmessagesequencetofindouttheexternalinterfaceoftheworkingversion.

2.Theintegrationtestcaseisdeterminedbytheexternalinterfaceoftheintegrationworkingversion.

3.Testcasesshouldcoverallmessageflowsequencesforeachexternalinterfaceoftheworkingversion.

Note:Therelationshipbetweenanexternalinterfaceandtestcasesismany-to-many.Thetestrequirementsofsomeintegratedworkingversionscanbemappedtosystemtestrequirements.Therefore,thesystemtestcasetechnologycanbereusedfortheseintegrationtestcases.

Workpiecelist

1.Softwareintegrationtestplan

2.Integrationtestcases

3.Testprocess

4.Testscript

5.Testlog

6.Testevaluationsummary

Selectionofcommonschemes

Summary

Overviewh3>

Therearemanyimplementationsolutionsforintegrationtesting,suchasbottom-upintegrationtesting,top-downintegrationtesting,Big-Bangintegrationtesting,sandwichintegrationtesting,coreintegrationtesting,layeredintegrationtesting,andusage-basedIntegrationtesting,etc.

Top-downtesting

Thetop-downintegrationmethodisanincrementalmethodofassemblingthesoftwarestructure.Startfromthemaincontrolmodule(mainprogram)andmovedownthecontrollayertocombinethemodulesonebyone.Therearetwomethods:

First:Depthfirst:Accordingtothestructure,useamaincontrolpathtocombineallmodules;

Second:Firstwidth:CombineallsubordinateslayerbylayerModulesmovehorizontallyalongeachfloor.

Theassemblyprocessisdividedintothefollowingfivesteps:

Step1:Usethemaincontrolmoduleasthetestdriver,andreplacethedirectsubordinatemodulewiththeundertakingmodule;

Step2:Accordingtotheselectedintegrationtestmethod(depthorwidthfirst),replacethesubordinateundertakingmodulewiththeactualmoduleeverytime

Step3:Testeachactualmodulewhencombining;

Step4:Aftercompletingasetoftests,useanactualmoduletoreplaceanotherundertakingmodule;

Step5:Youcanperformregressiontesting(thatis,doallorpartofitagain)Teststhathavebeendone)toensurethatnonewerrorsareintroduced.

Bottom-UpTesting

Bottom-UpIntegrationisthemostcommonlyusedmethod.Otherintegrationmethodshavemoreorlessinheritedandabsorbedtheideasofthisintegrationmethod.Thebottom-upintegrationmethodstartsassemblyandtestingfromthelowestmoduleintheprogrammodulestructure.Becausethemodulesareassembledfromthebottomup,foragivenlevelofmodule,itssub-modules(includingallsub-modulesofthesub-modules)havebeenassembledandtestedbeforehand,sothereisnoneedtocompilestubmodules(akindofenergy).Simulaterealmodulesandprovidetestsoftwaremodulesforcallinginterfacesordataforthemodulestobetested).Thebottom-upintegrationteststepsareroughlyasfollows:

Step1:Accordingtotheoutlinedesignspecification,specifywhichmodulesaretested.Onthebasisoffamiliaritywiththenatureofthetestedmodule,thetestedmodulesarelayered.Testsatthesamelevelcanbecarriedoutinparallel,andthenthesequenceoftestactivitiesissortedout,andthetestscheduleisformulated.Figure2showsthetopologicalrelationshipofeachtestactivityinthebottom-upintegrationtestprocess.Usingtherelevantknowledgeofgraphtheory,thetimeseriesrelationshipbetweenvariousactivitiescanbedischarged,andthetestingactivitiesatthesamelevelcanbecarriedoutatthesametimewithoutmutualinfluence.

Step2:OnthebasisofStep1,integratethesoftwareunitsintomodulesaccordingtothetimelinesequence,andtesttheproblemsthatoccurduringtheintegrationprocess.Here,testersmayneedtodevelopsomedrivingmodulestodrivethetestedmodulesformedintheintegrationactivities.Forlargermodules,youcanfirstintegratesomeofthesoftwareunitsintosub-modules,andthenintegratethemintoalargermodule.

Step3:Integratethesoftwaremodulesintosubsystems(orsub-systems).Checkwhethertherespectivesubsystemscanworknormally.Similarly,testersmayneedtodevelopasmallnumberofdrivermodulestodrivethetestedsubsystem.

Step4:Integrateeachsubsystemintoanend-usersystem,andtestwhethereachsubsystemcanworknormallyintheend-usersystem.

Suggestions:Thebottom-upintegrationtestprogramisthemostcommonlyusedtestmethodinengineeringpractice.Relatedtechnologiesarealsorelativelymature.Itsadvantagesareobvious:convenientmanagement,andtesterscanbetterlocatethelocationofsoftwarefaults.However,itisnotapplicabletosomedevelopmentmodels.Forexample,usingtheXPdevelopmentmethod,itwillrequiretesterstocompletetheintegrationtestofthecoresoftwarecomponentsbeforeallthesoftwareunitsareimplemented.Inspiteofthis,thebottom-upintegrationtestingmethodisstillareferenceintegrationtestingprogram.

Coresystemtesting

Theideaof​​thecoresystemintegrationtestingmethodistoconductintegrationtestingoncoresoftwarecomponentsfirst,andthenaccordingtotheimportanceofeachperipheralsoftwarecomponentafterthetestispassed.Integratedintothecoresystemonebyone.Eachtimeaperipheralsoftwarecomponentisadded,aproductbaselineisgenerated,untilastablesoftwareproductisformed.Theintegrationprocesscorrespondingtothecoresystemadvancedintegrationtestmethodisaspiralcurvethatgraduallytendstoclose,representingtheprocessofproductgradualfinalization.Thestepsareasfollows:

Step1:Carryoutaseparateandsufficienttestforeachmoduleinthecoresystem,usingdrivermodulesandstubmoduleswhennecessary;

Step2:ForAllmodulesinthecoresystemareassembledintothesystemundertestatonetimetosolvevariousproblemsinintegration.Inthecaseofarelativelylargecoresystem,thecomponentsofthecoresystemcanalsobeintegratedinabottom-upstep.

Step3:Accordingtotheimportanceoftheperipheralsoftwarecomponentsandthemutualrestrictionbetweenthemodules,drawupasequenceplanfortheintegrationoftheperipheralsoftwarecomponentsintothecoresystem.Aftertheplanisreviewed,theintegrationofperipheralsoftwarecomponentscanbecarriedout.

Step4:Beforetheperipheralsoftwarecomponentsareaddedtothecoresystem,theperipheralsoftwarecomponentsshouldcompletetheinternalmodule-levelintegrationtest.

Step5:Continuetoaddperipheralsoftwarecomponentsinorder,eliminateproblemsintheintegrationofperipheralsoftwarecomponents,andformthefinalusersystem.

Schemecomment:Thisintegratedtestingmethodisveryeffectiveforrapidsoftwaredevelopment,suitableforintegrationtestingofmorecomplexsystems,andcanensuretherealizationofsomeimportantfunctionsandservices.Thedisadvantageisthatthesystemusingthismethodshouldgenerallybeabletoclearlydistinguishbetweencoresoftwarecomponentsandperipheralsoftwarecomponents.Thecoresoftwarecomponentsshouldhaveahighdegreeofcoupling,andtheperipheralsoftwarecomponentsshouldalsohaveahighdegreeofcoupling.Thereshouldbealowdegreeofcouplingbetween.

High-frequencyintegrationtesting

High-frequencyintegrationtestingreferstotheintegrationtestingoftheexistingcodeofthedevelopmentteaminsynchronizationwiththesoftwaredevelopmentprocess.Forexample,someautomatedintegrationtestingtoolscanimplementanintegrationtestontheexistingcodeofthedevelopmentteamlateatnight,andthensendthetestresultstothee-mailofeachdeveloper.Theintegrationtestmethodfrequentlyaddsnewcodetoanalreadystablebaseline,soastopreventintegrationfailuresfrombeingdifficulttofind,andatthesametimecontrolpossiblebaselinedeviations.Theuseofhigh-frequencyintegrationtestingrequirescertainconditions:Astableincrementcanbeobtainedcontinuously,andtheincrementhasbeenverifiedtobenoproblem;mostofthemeaningfulfunctionincreasescanbeinarelativelystabletimeinterval(suchaseachObtainedwithinworkingdays);Thedevelopmentofthetestpackageandcodemustbecarriedoutinparallel,andversioncontroltoolsarerequiredtoensurethatthelatestversionofthetestscriptandcodeisalwaysmaintained;itmustbedonewiththehelpofautomatedtools.Anotablefeatureofhigh-frequencyintegrationisthefrequentintegrationtimes.Obviously,manualmethodsareincompetent.

High-frequencyintegrationtestingisgenerallycompletedbythefollowingsteps:

Step1:Chooseanintegrationtestautomationtool.Forexample,manyJavaprojectsusetheJunit+Antsolutiontoautomateintegrationtesting,andtherearealsosomecommercialintegrationtestingtoolstochoosefrom.

Step2:Setuptheversioncontroltooltoensurethattheversionobtainedbytheintegratedtestautomationtoolisthelatestversion.SuchasusingCVSforversioncontrol.

Step3:Testersanddevelopersareresponsibleforwritingtestscriptscorrespondingtotheprogramcode.

Step4:Setupanautomatedintegrationtesttool,performautomatedintegrationtestsonthenewlyaddedcodeoftheconfigurationmanagementlibraryatregularintervals,andreportthetestreporttothedevelopersandtesters.

Stepfive:Thetestersupervisesthecodedevelopertoclosetheunqualifieditemsinatimelymanner.

Followthesteps3to5tocontinuouslyloopuntilthefinalsoftwareproductisformed.

Schemecomment:Thetestplancanfindcodeerrorsintimeduringthedevelopmentprocess,andcanintuitivelyseetheeffectiveprojectprogressofthedevelopmentteam.Inthisscheme,thedevelopmentandmaintenanceofsourcecodeandthedevelopmentandmaintenanceofsoftwaretestpackagesaregiventhesameimportance,whichisveryhelpfultoeffectivelypreventerrorsandcorrectthemintime.Thedisadvantageofthisschemeisthatsometimesthetestpackagemaynotexposedeep-levelcodingerrorsandgraphicalinterfaceerrors.

Abovewehaveintroducedseveralcommonintegrationtestingsolutions.Generallyspeaking,intheintegrationtestingprocessofmoderncomplexsoftwareprojects,theintegrationtestingofthecoresystemisusuallycombinedwiththehigh-frequencyintegrationtesting.,Bottom-upintegrationtestingsolutionsaremorecommonintheintegrationprocessofsoftwareprojectsthatadoptthetraditionalwaterfalldevelopmentmodel.Readersshouldmakeareasonableselectionbasedontheactualengineeringenvironmentoftheprojectandtheapplicablescopeofeachtestplan.

Plan

Introduction

1.1PurposeofWriting

Thisarticleisanoutlinearticledescribing****integrationtesting,mainlydescribinghowConductintegrationtestingactivities?Howtocontrolintegrationtestingactivities?Theprocessofintegrationtestingactivitiesandtheworkarrangementofintegrationtestingactivities.Themainreadersofthisarticleareprojectleaders,integrationdepartmentmanagers,andintegrationtestdesigners.

1.2Background

Projectname:***Integrationtest

Projectrelatedobjects:*****************

1.3Definition

**********:********************

1.4ReferenceMaterials

《*********》

Testitems

Thistestismainly***Systemintegrationtest.Theversionof***is2.0.Thetestisthefinalintegrationtestof***.Itisbasedonthedevelopmentteamprogrammerswhohavecompletedtheirowntestsandthedevelopmentteamtests.

Testedcharacteristics

3.1Operationaltest

Isthemaintestoperationcorrect,andisthereanyerror?Itisdividedintotwoparts:

3.1.1Returntest

Stepbystepfromthemaininterfacetothefinalinterface,presstheEXITkeytoreturnstepbystep,andcheckifthescreenfocusiscorrectwhenreturning

Forexample:

1.Enter"SystemSettings"

2.Enter"ChannelSearch"

3.Enter"AutoChannelSearch"

4.PresstheEXITkeytoreturnandcheckwhetherthecurrentfocusis"ChannelSearch"

5.PresstheEXITkeytogobackandcheckwhetherthecurrentfocusis"SystemSettings"

3.1.2Enterthetest

Stepbystepfromthemaininterfacetothefinalinterface,presstheMENUkeytoreturntothemaininterface,enteragain,andcheckifthefocusiscorrect

Forexample:

1.Enter"SystemSettings"

2.Enter"ChannelSearch"

3.Enter"AutoChannelSearch"

4.PressMENUKeytoreturntothemaininterface

5.Whetherthecurrentfocusis"SystemSettings"

6.Enter"SystemSettings",whetherthecurrentfocusis"ChannelSearch"

3.2Functiontest

Testwhetherthefunctionofeachapplicationintheset-topboxiscorrect

3.3Performancetest

3.3.1Fatiguetest

Testthedevicetoruntheapplicationevery3dayswithoutshuttingdownthedeviceafterbeingturnedoncontinuouslyfor1month.Lookatthestabilityofthesystem

3.3.2Large-capacitydatatest

Thepreviousparagraph***databasetablecontainsalargeamountofdata,testthe***function

NoTestedfeatures

Testmethod

1.Writetestplan

2.Reviewtestplan,returntothefirststepifitfails

3.Writetestcases;

4.Reviewtestcases,returntothethirdstepiftheyfail

5.TestersconducttestsaccordingtotestcasesonebyoneActivities,andfillinthetestresultsonthetestreport;(thetestreportmustcoveralltestcases)

6.Ifabugisfoundduringthetest,fillinthebugonbugzillaandsendittotheintegrationmanager;(bugStatusNEW)

7.Theintegrationmanagerreceivesabugsentbybugzilla

7.1Forobviousbugsthatcanbesolvedimmediately,sendthebugtothedeveloper;(bugstatusASSIGNED);

7.2Forsubmissionsthatarenotbugs,theintegrationmanagerinformsthetestdesignersandtesterstomodifythecorrespondingdocuments;(bugstatusisRESOLVED,decidedtosettoINVALID);

7.3Forthosethatcannotbemodified,putthebuginthenextroundformodification;(bugstatusisRESOLVED,decidedtosetittoREMIND)

8.Developerswillimmediatelymodifythebugsentover;(ThebugstatusisRESOLVED,decidedtosetittoFIXED)

9.Whenthetesterreceivestheerrorchangeinformationsentbybugzilla,heshouldretestitembyitemandfillinanewtestreport(thetestreportmustcoverthepreviousoneAllREOPENEDtestcases);

10.Ifthereisaproblemintheretest,returntostep6(bugstatusREOPENED)

11.Otherwise,closethisBUG(bugstatusCLOSED)

12.Inthisroundoftesting,95%ofthetestcasespassedthetestatonetime,andthetesttaskended;

13.98%oftheerrorsfoundinthisroundoftestingweremodifiedandpassedTestagain(thatis,thebugstatusisCLOSED),andreturntothefifthstepforanewroundoftesting;

14.Writeatestsummaryreportafterthetesttaskisover;

15.TheregulartestisoverEntertheinformaltest,thefirstistheALPHAtest,askothernon-technicalpersonnelinthecompanytousethesystemasauser.Ifabugisfound,thetesterisnotified,andthetesterhandlesthebugincidentinaformalprocess;

16.ThenthereistheBETAtest,andtheuserrepresentativeisinvitedtoperformthetest.Ifabugisfound,thetesterisnotified,andthetesterhandlesthebugincidentinaformalprocess.

Someexplanations:

Otestregressionplanisthreetimes;

Otestcasesshouldbewritteninmoredetail,andthestepsmustbeclearlymarked(shouldinclude:Number,testdescription,preconditions,teststepsanddesiredresultsofthetest);

OForthetestitemsthatthetesterthinksshouldbecarriedout,thetestershouldreporttothetestdesignertoimproveandperfectthetestcase;

OThetestreportisseparatedfromthetestcase.ThetestreportindicatestheserialnumberofthetestcaseandwhetheritpassesY/N;

Oforthedecisionoftheprojectleaderthattheintegrationmanagercannotdecide;

ThefatiguetestintheOperformancetestcanbecombinedinthefunctiontestpart,thatis,themachineisnotturnedoffduringthetest;

Thelarge-capacitydatatestintheOperformancetestisplacedinthepartofthetestafterthetest.(Thesecondstep,onlyneedtobedoneonce)

TestPassStandard

Thetestresultisconsistentwiththeexpectedresultinthetestcase,thetestpassed,otherwisethetestfailed.

6.1Testresultapprovalprocess

6.1.1Endoftestregressionapplication

Thetesterappliesfortheendofthisroundoftestingandsubmitsittothemanageroftheintegrationdepartment;

ThemanageroftheIntegrationDepartmentconvenedameetingoftheteamtodiscuss;

Thediscussionpassed,thenextroundoftesting,anddeploymentofthenextroundoftestingprecautions,proceduresandothercontent;

Ifyoufindthattherearestillproblemsinthisroundoftestingthathavenotbeenresolved,postponethenextroundoftestingtodiscusshowthenextstepshouldbedone.

6.1.2Testresultapplicationisover

Thetestersubmitsanapplicationandsubmitsthetesttothemanageroftheintegrationdepartment;

Themanageroftheintegrationdepartmentconvenesameetingwiththegroupofpeopletodiscuss;

1.Passthediscussionandendthetesttask;

2.Ifitisfoundthattherearestillproblemsinthetestthathavenotbeenresolved,postponetheendofthetestanddiscusshowthenextstepshouldbedone.

Suspendandresume

7.1Suspendconditions

OEnterthefirstroundoftesting,thetesterwillgetageneralunderstandingoftheproductsituation,ifwithinanhourIfmorethan5(including5)operationalerrorsarefound,ormorethan3(including3)functionalerrorsarefound,returntothetestgroupfortesting;

OencounteranintegrationtestwithahigherprojectpriorityTask;

Oencounteredahigherpriorityintegrationtask;

Ofoundthattheproductcouldnotrunduringthetestretest;

OInsufficientpersonnelandequipment.

7.2Recoveryconditions

OMeettheconditionsforenteringtheintegrationtest(5orless(notincluding5)operationalerrorsfoundwithinonehour,or3orless(notincluding3)A)functionalerror);

TheintegrationtesttaskwithhigherpriorityoftheOprojecthasbeentemporarilycompleted;

TheintegrationtaskwithhigherpriorityoftheOprojecthasbeentemporarilycompleted;

p>

Otheproductcancontinuetorunduringtheretest;

Opersonnel,theequipmentisinplace.

Testfile

Otestplan

Otestcase

Otestreport

Otestsummary

Testtasks

ODevelopanaudittestplan

ODevelopandreviewtestcases

Ocarryouttestingactivities

OWritingtestreports

Testenvironmentrequirements

10.1Hardwarerequirements

***********

10.2SoftwareRequirements

************

10.3TestTool

*************

10.4Conditionsneededfortesting

**************

10.4.1Requireddocuments

OUserManual

OApplicationManual

OInstallationInstructions

10.4.2Taskstobecompleted

OTheprogrammerhimselftests

OThetestteamcompletesthetest

Rolesandresponsibilities

OIntegration(test)manager:Controlandcompletethetesttasksandtestprocess,Decidewhetherthebugsubmittedbythetesterneedstobemodified;

Otestdesigner:writeintegrationtestcases;

Otester:performtestactivitiesaccordingtotestcases;

Odeveloper:MHPprogrambugmodification;

Ouserrepresentative:conductBETAtest.

Personnelandtraining

Ointegrationtestmanagerhastheresponsibilitytoconducttestproceduresandrulesandregulationstrainingfortest-relatedpersonnel;

OtestdesignershavetheresponsibilitytotestPersonnelconducttestoperationtraining

Testprogress

Testworkprogress(person*workingdays)

Testplan8

Testdesign60

Thetotalprogressoftestexecutionis30

Theprogressofeachregressionis10

Testreport2

Riskandcontingencyplan

Equipmentisnotinplace:stepupequipmentpurchase;

Insufficientpersonnel

Personnelleave:leavepersonneltoworkovertimeorquicklytestprogress/applyfornewpersonnel;

Staffresignation:deploynewpersonnel;

Relocatepersonneltootherdepartmentsorprojects:deploynewpersonnel;

Developersmakefrequentmistakesindevelopment:notifythedevelopmentdepartmentanddiscussstrategies;

Thetestworkforotherreasonsisfrequentlysuspendedorcannotberesumedaftersuspension:overtimeorpostponement

Approval

IntegrationDepartmentManager,TechnicalDepartmentManager

Name:Name:

Date:Date:

Comparisonofunittests

Differentunitstested

Unittestingisatestforthebasicunitsofthesoftware(suchasfunctions),whileintegrationtestingisatestperformedonmodulesandsubsystemsasaunit,mainlytestingtherelationshipbetweeninterfaces.

Thebasisofthetestisdifferent

Unittestingisatestforthedetaileddesignofthesoftware,andthemainbasisofthetestcaseisalsothedetaileddesign.Theintegrationtestisatestforthegeneraldesignofthesoftware,andthemainbasisofthetestcaseisthegeneraldesign.

Differenttestspaces

Integrationtestsmainlytestthetestspaceoftheinterfacelayer,andunittestsmainlytestthetestspaceoftheinternalimplementationlayer.

Differenttestingmethodsareused

Integrationtestingfocusesontheintegrationofinterfaces,andunittestingonlyfocusesonasingleunit,sothespecifictestingmethodsarealsodifferent.

Tento článek je ze sítě, nereprezentuje pozici této stanice. Uveďte prosím původ dotisku
HORNÍ