linkedin test plan
DESCRIPTION
This is the test Plan.TRANSCRIPT
-
Week#3
TestPlanning
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation 1
ByDr.Vidhyacharan Bhaskar
-
Agenda
1. Whatisatestplan?2. Whyweneedtestplan?3. TestPlanningComponents4. Howtowriteatestplan5. TestStrategy6. RTM(RequirementTraceabilityMatrix)
2NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
TestinginSDLC
3
WhatisSoftwareTestingLifeCycle(STLC)? 1.RequirementStudy 2.TestPlanning 3.WritingTestCases 4.ReviewtheTestCases 5.ExecutingtheTestCases 6.Bugloggingandtracking 7.CloseorReopenbugs
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Whatisatestplan?
4
Areyoufeelingpreferenceorlogicalpreference?
Whenwetravel,dowehaveplan?...
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Whatisatestplan?
5
ATestPlanisadocumentdescribingthescope,approach,resources,andscheduleofintendedtestingactivities.Itidentifiestestitems,thefeaturestobetested,thetestingtasksandwhowilldoeachtask(rolesandresponsibilities)andanyrisksanditssolutions.
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Whatisatestplan?
6
ATestPlanincludesHeading,RevisionHistory,TableofContents,Introduction,Scope,Approach,Overview,differenttypesoftestingthatwillbecarriedout,whatsoftwareandhardwarewillberequired,issues,risks,assumptionsandsignoffsection.
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Whatisatestplan?
7
IEEE829STANDARDTESTPLANTEMPLATETestplanidentifierTestdeliverablesIntroductionTesttasksTestitemsEnvironmentalneedsFeaturestobetestedResponsibilitiesFeaturesnottobetestedStaffingandtrainingneedsApproachScheduleItempass/failcriteriaRisksandcontingenciesSuspensionandresumptioncriteriaApprovals
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
WhyweneedtestplanWhatisthepurposeandimportanceoftestplansinsoftwaretesting?
1. Bywritingatestplanitguidesourthinking.2. Thetestplanningprocessandtheplanitself
serveasthemeansofcommunicationwithothermembersoftheprojectteam,testers,peers,managersandotherstakeholders.
3. Thetestplanhelpsustomanagechange.
8NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Whyweneedtestplan
9
TestPlantellsthetesterthatwhatneedstobetestedandhowtestingisgoingtobeperformed.Testplanalsotellsthatwhatresourcesareneededfortheexecutionofthetestcases,timelinesandriskassociatedwiththetestplan.
Wecanalsoperformthetestingwithouttestplandocument,butfirstwehavetoselecttestApproachforthetestingandgowithtesting.
Manytestplansarebeingcreatedjustforthesakeofprocesses.
Manytesterusetestplandocumentswhentestplandocumentcontainsthesomeusefulinformation.
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
TestPlanningComponents
10
1. TestScope whattotest,whatnottotest(OutofScope)2. TestObjectives whytest3. Assumptions whatweknowordontknowaboutUAT4. RiskAnalysis whathappenifwedonttest5. TestDesign scenariosandtestcases6. Roles&Responsibilities whoistodowhat7. TestSchedule&Resources time,milestone(checkpoint)8. TestDataManagement whatresourcesandinfrastructures9. TestEnvironment machines,databases10. CommunicationApproach sharinginfoordoccenter11. TestTools testmanagementtoolorfunctiontestingtool12. ExitCriteria whentostoptesting
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Howtowriteatestplan
11
HowtoWriteaTestPlanDocument SampleTestPlanDocumentforOrangeHRMProject
GenericTestPlan NPUWebPage
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
TestStrategy
12
Ateststrategyisanoutlinethatdescribesthetestingportionofthesoftwaredevelopmentcycle.Itiscreatedtoinformprojectmanagers,testers,anddevelopersaboutsomekeyissuesofthetestingprocess.Thisincludesthetestingobjective,methodsoftestingnewfunctions,totaltimeandresourcesrequiredfortheproject,andthetestingenvironment.
Theteststrategydescribeshowtheproductrisksofthestakeholdersaremitigatedatthetestlevel,whichtypesoftestaretobeperformed,andwhichentryandexitcriteriaapply.(source:Wikipedia)
Theteststrategyiscreatedbasedondevelopmentdesigndocuments.ItiswrittenbytheTestManagerorLead.
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
TestStrategy
13
ThefollowingaresomeofthecomponentsthattheTestStrategyincludes:
1TestLevels.2RolesandResponsibilities.3EnvironmentRequirements.4TestingTools.5RisksandMitigation.6TestSchedule.7RegressionTestApproach.8TestGroups.9TestPriorities.10TestStatusCollectionsandReporting.11TestRecordsMaintenance.12Requirementstraceabilitymatrix.13TestSummaryCheckhowtheTestStrategylookslike inWWW.
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
RTM(RequirementTraceabilityMatrix)
14
TraceabilityMatrix isamethodusedtovalidatethecomplianceofproductwithrequirementsforthatproduct.Therequirementiswritteninarowofthematrixandthecolumnsofthematrix.Itisusedtocrosscheckthetestcasesaspertherequirementofthetestcases. Inotherwords,itcheckswhethertheeachfunctionalityiscoveredintheTestCasesasperrequirementdocument. (WecreateRTMusingQualityCentertool)
Howtocreaterequirementstestmatrixtemplate
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Exercise
15
1. ReadTextBookChapter3.23.72. ReadAppendixA(TestPlanAccordingtoIEEE
Standard8291998)
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
SelfcheckQuestions
16
1. HaveyouwrittenTestPlan?WhatisaTestPlan?Whatdoesitinclude?
2. Whatarethedifferencesbetweenteststrategyandtestplan?
3. Howdoyouprioritizetestingtaskswithinaproject?
4. WhatisTraceabilityMatrix?HowtocreateRTM(RequirementTraceabilityMatrix)Template?
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
SelfcheckQuestions
17
5.WhatarethedimensionsoftheRisks?6.Whatifthereisntenoughtimeforthoroughtesting?7.Whatarethefactorsresponsiblefortheestimationofsystemintegrationtestcycleandtotalintegrationtime?8.WhatisChangeControl(ORChangeRequest)?
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Assignment(Homework)
18
HW3Createaneffectivetestplanforafeaturechoosingfromfollowingdomains
(1)ECommerce Amazon,eBay,TOYOTA(2)Financials BankofAmerica(3)InternetServiceProvider Yahoo,Google(4)SocialMedia Facebook,LinkedIn,Twitter(5)CloudComputing Salesforce(6)HealthCare CoveredCalifornia
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
Assignment(Homework)
19
HW3Thetestplanshouldchoosefiveormorecomponentsfrom:
TestScope,OutofScope,TestObjectives,Assumptions,RiskAnalysis,TestDesign,Roles&Responsibilities,TestSchedule&Resources,TestDataManagement,TestEnvironment,CommunicationApproach,TestTools,ExitCriteria.
http://www.softwaretestinghelp.com/howtowritetestplandocumentsoftwaretestingtrainingday3/
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
www.SoftwareTestingHelp.comTestPlan(aRealSample)SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM2/1/2014SoftwareTestingHelp.comNameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveprojectfortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject
Version:1.0Created:02/05/2014LastUpdated:02/05/2014Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsignoff)
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage1
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version Date Author Description of Change
1 02/14/2014 Swati Seela Draft
2 02/14/2014 Vijay Shinde Draft - Reviewed
ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name Role Approver/ReviewerApproval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version Date DocumentName
1.0 ORANGEHRMVERSION3.0 MYINFOMODULE FSD
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage2
TableofContents
1. INTRODUCTION........................................................................................................................4
1.1. Purpose.........................................................................................................................4
1.2. ProjectOverview..........................................................................................................4
1.3. Audience.......................................................................................................................4
2. TESTSTRATEGY........................................................................................................................5
2.1. TestObjectives.............................................................................................................5
2.2. TestAssumptions.........................................................................................................5
2.3. TestPrinciples...............................................................................................................6
2.4. DataApproach..............................................................................................................6
2.5. ScopeandLevelsofTesting..........................................................................................6
2.5.1. Exploratory......................................................................................................6
2.5.2. FunctionalTest................................................................................................7
TESTACCEPTANCECRITERIA...........................................................................7
TESTDELIVERABLES.........................................................................................7
MILESTONELIST..............................................................................................8
2.5.3. UserAcceptanceTest(UAT)............................................................................8
TESTDELIVERABLES.........................................................................................8
2.6. TestEffortEstimate......................................................................................................9
3. EXECUTIONSTRATEGY.............................................................................................................9
3.1. EntryandExitCriteria...................................................................................................9
3.2. TestCycles..................................................................................................................10
3.3. ValidationandDefectManagement..........................................................................10
3.4. TestMetrics................................................................................................................11
3.5. Defecttracking&Reporting.......................................................................................12
4. TESTMANAGEMENTPROCESS..............................................................................................12
4.1. TestManagementTool..............................................................................................12
4.2. TestDesignProcess....................................................................................................13
4.3. TestExecutionProcess...............................................................................................14
4.4. TestRisksandMitigationFactors...............................................................................14
4.1. CommunicationsPlanandTeamRoster....................................................................16
4.2. RoleExpectations.......................................................................................................16
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage3
4.2.1. ProjectManagement.....................................................................................16
4.2.2. TestPlanning(TestLead)..............................................................................16
4.2.3. TestTeam......................................................................................................17
4.2.4. TestLead.......................................................................................................17
4.2.5. DevelopmentTeam.......................................................................................17
5. TESTENVIRONMENT..............................................................................................................17
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage4
1. INTRODUCTION1.1. Purpose
ThistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingoftheOrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,datastrategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocesstoidentifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthatcomeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,teamroster)
1.2. ProjectOverviewMyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoviewrelevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternetenabledPCwithouthavingtoinvolvetheHRdepartment.
The functionality of this module spans through the entire system, making information availableanywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecanonlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESSModule,maintainingthesecurityandconfidentialityofemployeeinformation
1.3. Audience Project team members perform tasks specified in this document, and provide input and
recommendationsonthisdocument. Project Manager Plans for the testing activities in the overall project schedule, reviews the
document,trackstheperformanceofthetestaccordingtothetaskhereinspecified,approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants (individualsas identifiedby thePMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsofthetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththedesign,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesofdefects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage5
2. TESTSTRATEGY2.1. TestObjectives
Theobjectiveofthetest istoverifythatthefunctionalityofORANGEHRMVERSION3.0MY INFOMODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseveritydefectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware; AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtestexecution.
2.2. TestAssumptionsKeyAssumptions
ProductionlikedatarequiredandbeavailableinthesystempriortostartofFunctionalTesting Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting Performancetestingisnotconsideredforthisestimation. AllthedefectswouldcomealongwithasnapshotJPEGformat TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPNconnectivity TheTestTeamassumesallnecessary inputs requiredduringTestdesignandexecutionwillbe
supportedbyDevelopment/BUSINESSANALYSTsappropriately. TestcasedesignactivitieswillbeperformedbyQAGroup TestenvironmentandpreparationactivitieswillbeownedbyDevTeam DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeachcycletoplan.The
samewillbeinformedtoTestteampriortostartofDefectfixcycles BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTestTeampriortostartof
Testexecution ThedefectswillbetrackedthroughHPALMonly.AnydefectfixesplannedwillbesharedwithTest
TeampriortoapplyingthefixesontheTestenvironment ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltestdeliverables Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport Test team will manage the testing effort with close coordination with Project PM/BUSINESS
ANALYST Projectteamhastheknowledgeandexperiencenecessary,orhasreceivedadequatetrainingin
thesystem,theprojectandthetestingprocesses. Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage6
Thesystemwillbe treatedasablackbox; if the informationshowscorrectlyonlineand in thereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.
FunctionalTesting DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailableonthesystemat
thetimeofexecution TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRMVERSION3.0MYINFO
MODULE
UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQAGroupwillprovidetheirsupportoncreatingUATscript.
2.3. TestPrinciples Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,andquality. Therewillbecommon,consistentproceduresforallteamssupportingtestingactivities. Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeasneeded. Testingactivitieswillbuilduponpreviousstagestoavoidredundancyorduplicationofeffort. Testingenvironmentanddatawillemulateaproductionenvironmentasmuchaspossible. Testingwillbearepeatable,quantifiable,andmeasurableactivity. Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectivesandgoals. Therewillbeentranceandexitcriteria.
2.4. DataApproach Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwillcontainpreloadedtestdata
andwhichisusedfortestingactivities.
2.5. ScopeandLevelsofTesting2.5.1. Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbeforethenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytestscriptsanddocumentation
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage7
TIMING:atthebeginningofeachcycle.
2.5.2. FunctionalTestPURPOSE: Functional testingwillbeperformed to check the functionsofapplication.Thefunctional testing is carried out by feeding the input and validates the output from theapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:Thescope ishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeenembeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.ThescopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.
Functional Testing
Scope.xlsx
TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whicharestoredinHPALM.
TIMING:afterExploratorytestiscompleted.
TESTACCEPTANCECRITERIA1. ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbeavailable
priortostartofTestdesignphase.2. TestcasesapprovedandsignedoffpriortostartofTestexecution3. Developmentcompleted,unittestedwithpassstatusandresultssharedtoTestingteam
toavoidduplicatedefects4. Testenvironmentwithapplicationinstalled,configuredandreadytousestate
TESTDELIVERABLES
Signoff
ApprovedFunctionalSpecificationDocumentApprovedUsecasesApprovedTestcases
Readiness
Developmentcompleted&unittestedApplicationdeployedandsystemreadyfortestingonTestenvironmentProductionlikedataisavailabletotestallfunctionalities.DefectfixesplannedbasedonDefecttriage(UnitTesting)andevaluationcriteria
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage8
S.No. DeliverableName Author Reviewer1. TestPlan TestLead Project Manager/
BusinessAnalysts2. FunctionalTestCases TestTeam Business Analysts
Signoff3. LoggingDefectsinHPALM TestTeam Test Lead/
ProgrammingLead(Vijay)
(4. Daily/weeklystatusreport TestTeam/TestLead Test Lead/ ProjectManager
5. TestClosurereport TestLead ProjectManager
MILESTONELISTThemilestonelististentativeandmaychangeduetobelowreasons
a) AnyissuesintheSystemenvironmentreadinessb) Anychangeinscope/additioninscopec) Anyotherdependencythatimpactseffortsandtimelines
Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,wecanestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseeinthebelowembeddedexcelsheet.
DFRT Execution Cycle.xlsx
2.5.3. UserAcceptanceTest(UAT)PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheenduserstocompleteonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemost indicatedtoprovide inputaroundbusinessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdosomevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbasedontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Onlyafterthistestiscompletedtheproductcanbereleasedtoproduction.
TESTDELIVERABLES
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage9
S.No. DeliverableName Author Reviewer1. UATTestCases TestTeam Business Analysts
Signoff
2.6. TestEffortEstimateThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshowmanymanhourseachactivityisgoingtotake.
3. New_Detailed DRFT Test estimate v1.xlsx
Note:thisestimateisfortheTCOEteamonlyTestingSchedule
4. EXECUTIONSTRATEGY4.1. EntryandExitCriteria
The entry criteria refer to the desirable conditions in order to start test execution; only themigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
The exit criteria are the desirable conditions that need to bemet in order proceedwith theimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteamwillassesstherisk, identifymitigationactionsandprovidea recommendation.All this is input to theprojectmanagerforafinalgonogodecision.
Entry criteria to start theexecutionphaseof the test: theactivities listed in theTestPlanningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsectionofthescheduleare100%completedateachcycle.
ExitCriteria TestTeamTechnicalTeam Notes
100%TestScriptsexecuted
95%passrateofTestScripts
NoopenCriticalandHighseveritydefects
95%ofMediumseveritydefectshavebeenclosed
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage10
AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease
Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
AlltestmetricscollectedbasedonreportsfromHPALM
AlldefectsloggedinHPALM
TestClosureMemocompletedandsignedoff
Testenvironmentcleanupcompletedandanewbackupoftheenvironment
4.2. TestCycleso Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteallthescripts.o Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,andmostofthehigh
defects.Itisexpectedtousesomeworkaroundinordertogettoallthescripts.o Theobjectiveofthesecondcycleistoidentifyremaininghighandmediumdefects,remove
theworkaround from the first cycle, correct gaps in the scripts andobtainperformanceresults.
UATtestwillconsistofonecycle.
4.3. ValidationandDefectManagement Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribedabove.However
itisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifyapossiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusinessanalystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshaveadeeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceabilitymatrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.ThetechnicalteamwillgatherinformationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefectCoordinator.Thetechnicalteamwillworkonfixes.
It is the responsibilityof the tester toopen thedefects, link them to thecorrespondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itistheresponsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththetechnicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcancontinueorshouldbehalt,requestthe tester to retest, and modify status as the defect progresses through the cycle; it is theresponsibilityofthetechnicalteamtoreviewHPALMonadailybasis,askfordetailsifnecessary,
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage11
fixthedefect,communicatetotheDefectManagerthefixisdone,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHPALMandthecategoriesare:
Severity Impact1(Critical) Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,or
causepotentialdataloss Itcausesanabnormalreturntotheoperatingsystem(crashorasystem
failuremessageappears). Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High) Itcausesalackofvitalprogramfunctionalitywithworkaround.3(Medium) ThisBugwilldegradethequalityoftheSystem. Howeverthere isan
intelligent workaround for achieving the desired functionality forexamplethroughanotherscreen.
This bug prevents other areas of the product from being tested.Howeverotherareascanbeindependentlytested.
4(Low) Thereisaninsufficientorunclearerrormessage,whichhasminimumimpactonproductuse.
5(Cosmetic)
Thereisaninsufficientorunclearerrormessagethathasnoimpactonproductuse.
4.4. TestMetricsTestmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwiththeprojectmanagerforapproval.Thebelowaresomeofthemetrics
Report Description Frequency
Testpreparation&ExecutionStatus
Toreporton%complete,%WIP,%Pass,%Fail
DefectsseveritywiseStatusOpen,closed,anyotherStatus
Weekly/Daily(optional)
Dailyexecution
status
ToreportonPass,Fail,Totaldefects,highlightShowstopper/Criticaldefects
Daily
ProjectWeekly
Projectdrivenreporting(AsrequestedbyPM) WeeklyIfprojectteamneedsweekly
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage12
4.5. Defecttracking&ReportingFollowingflowchartdepictsDefectTrackingProcess:
5. TESTMANAGEMENTPROCESS
5.1. TestManagementToolHPApplicationLifecycleManagementisthetoolusedforTestManagement.AlltestingartifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycleManagement(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatusofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccesstoadd/modifyTestcasesinHPALM.
Statusreport
updateapartfromdailyandthereistemplateavailablewithprojectteamtouse.
Appr
Start
Tester: DevLead
Developer:
Tester:
R t t
N
Stop
Cl
Y
TestLead
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage13
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethestatusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTestcase/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythedefectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTestexecution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopendefects,Severitywisedefectsetc.
5.2. TestDesignProcess
Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcasetoensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartofTraceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthereviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereviewdefectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctionalspecificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbesharedperiodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.TheclarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicitrequirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusinessAnalysts. AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHPALM.
UnderstandingRequirements
EstablishingTraceabilityMatrixinHP
ALM
PreparationofTestcases
SME/PeerReviewofTest
cases
IncorporatingReview
commentsintestcases
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage14
5.3. TestExecutionProcess
OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM. Testerstoensurenecessaryaccesstothetestingenvironment,HPALMforupdating
teststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturntotheProjectManagerasescalation.
IfanyshowstopperduringexploratorytestingwillbeescalatedtotherespectivedevelopmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.ThetesterentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtooldetailing
stepstosimulatealongwithscreenshotsifappropriate. DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoallstakeholders. Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltestcases
areexecutedwitheitherpass/failcategory. Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthespecificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus. Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresultswillbe
updatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
5.4. TestRisksandMitigationFactors
Risk Prob. Impact Mitigation Plan
SCHEDULE High High Thetestingteamcancontrolthepreparationtasks(inadvance)
Executeeachoftheteststepin
testcase
MarkStatusasPass/FailinHP
ALM
RaisedefectsforthefailedtestcasesinHPALM
Sendthedailystatusreportto
TestLead
ParticipateinDefectTriage
cycleandexplainthedefects
Completethetestexecutionofallthetestcases
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage15
Risk Prob. Impact Mitigation Plan
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbeextendedbeyondtheUATscheduledstartdate.
andtheearlycommunicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotasmuchasbestpracticesadvise.
RESOURCESNotenoughresources,resourcesonboardingtoolate(processtakesaround15days.
Medium High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimationcouldderiveindelaysinthetesting.
DEFECTSDefectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybeduetounclearspecificationsandaretimeconsumingtoresolve.
Medium High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPEScopecompletelydefined
Medium Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventinoneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility Medium High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartofTestexecution.
DelayedTestingDueTonewIssues
Medium High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomeanissuethatwilltaketimetoresolve.Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.Thesedefectscanyieldtoanissuethatwillneedtimetoberesolved.
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage16
Risk Prob. Impact Mitigation Plan
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplacetoimmediatelyprovidearesolution.
5.1. CommunicationsPlanandTeamRoster5.2. RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthemanagement,planningorexecutionofthetestfortheproject.
Roles Name ContactInfo
1. ProjectManager
2. TestLead
3. BusinessAnalyst
4. DevelopmentLead
5. TestingTeam
6. DevelopmentTeam
7. TechnicalLead
5.2.1. ProjectManagement ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTestEstimates
signsoffonit.
5.2.2. TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution. Developtestplanandtheguidelinestocreatetestconditions,testcases,expectedresults
andexecutionscripts. Provideguidelinesonhowtomanagedefects. Attendstatusmeetingsinpersonorviatheconferencecallline.
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage17
Communicatetothetestteamanychangesthatneedtobemadetothetestdeliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport. Provide functional (Business Analysts) and technical team to test team personnel (if
needed).
5.2.3. TestTeam Developtestconditions,testcases,expectedresults,andexecutionscripts. Performexecutionandvalidation. Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedbytheTest
lead. Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule. Preparetestingmetricsandprovideregularstatus.
5.2.4. TestLead Acknowledgethecompletionofasectionwithinacycle. GivetheOKtostartnextleveloftesting. Facilitate defect communications between testing team and technical / development
team.
5.2.5. DevelopmentTeam Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)andprovide
timelyfeedback. Assistinthevalidationofresults(ifrequested). Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject. Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthepoints
specifiedinthetestingschedule. Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydateslipsbased
onthecurrentschedule. Defineprocesses/toolstofacilitatetheinitialandongoingmigrationofcomponents. Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttestexecutorsin
creationofaccuratedefects. Implementfixestodefectsaccordingtoschedule.
6. TESTENVIRONMENT
ORANGEHRM VERSION 3.0 MY INFO MODULEs servers will be hosted at X companys site. RANGEHRM VERSION 3.0 MY INFO MODULE will be hosted on two servers: One to host the actual website and (language) code, and the other to host the (database name) database.
-
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
CompanyconfidentialPage18
AwindowsenvironmentwithInternet Explorer 8, 9 and 10, and with Firefox 27.0, as well as Google Chrome 32.0 and later should be available to each tester.
7. APPROVALS
TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:
Name: Role: Date:
Signature:
Name: Role: Date:
Note: This is a sample test plan created on real time software testing liveprojecttrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject
CS522_Week03Live-Project_Test-Plan_SoftwareTestingHelp