LInkedin Test Plan

Week#3
TestPlanning
ByDr.Vidhyacharan Bhaskar
NPU2015SpringCS522(A)(B)(C)(F)(G) SoftwareQualityAssuranceandTestAutomation
Agenda
1.
2.
3.
4.
5.
6.
Whatisatestplan?
Whyweneedtestplan?
TestPlanningComponents
Howtowriteatestplan
TestStrategy
RTM(RequirementTraceabilityMatrix)
TestinginSDLC
WhatisSoftwareTestingLifeCycle(STLC)?
1.RequirementStudy
2.TestPlanning
3.WritingTestCases
4.ReviewtheTestCases
5.ExecutingtheTestCases
6.Bugloggingandtracking
7.CloseorReopenbugs
Whatisatestplan?
Areyoufeelingpreferenceorlogical
preference?
Whenwetravel,dowehaveplan?...
Whatisatestplan?
ATestPlanisadocumentdescribingthe
scope,approach,resources,andscheduleof
intendedtestingactivities.Itidentifiestest
items,thefeaturestobetested,thetesting
tasksandwhowilldoeachtask(rolesand
responsibilities)andanyrisksandits
solutions.
Whatisatestplan?
ATestPlanincludesHeading,RevisionHistory,
TableofContents,Introduction,Scope,
Approach,Overview,differenttypesoftesting
thatwillbecarriedout,whatsoftwareand
hardwarewillberequired,issues,risks,
assumptionsandsignoffsection.
Whatisatestplan?
IEEE829STANDARDTESTPLANTEMPLATE
Testplanidentifier
Testdeliverables
Introduction
Testtasks
Testitems
Environmentalneeds
Featurestobetested
Responsibilities
Featuresnottobetested
Staffingandtrainingneeds
ApproachSchedule
Itempass/failcriteria
Risksandcontingencies
SuspensionandresumptioncriteriaApprovals
Whyweneedtestplan
Whatisthepurposeandimportanceoftestplansin
softwaretesting?
1. Bywritingatestplanitguidesourthinking.
2. Thetestplanningprocessandtheplanitself
serveasthemeansofcommunicationwith
othermembersoftheprojectteam,testers,
peers,managersandotherstakeholders.
3. Thetestplanhelpsustomanagechange.
Whyweneedtestplan
TestPlantellsthetesterthatwhatneedstobetested
andhowtestingisgoingtobeperformed.Testplan
alsotellsthatwhatresourcesareneededforthe
executionofthetestcases,timelinesandrisk
associatedwiththetestplan.
Wecanalsoperformthetestingwithouttestplan
document,butfirstwehavetoselecttestApproachfor
thetestingandgowithtesting.
Manytestplansarebeingcreatedjustforthesakeof
processes.
Manytesterusetestplandocumentswhentestplan
documentcontainsthesomeusefulinformation.
TestPlanningComponents
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
TestScope whattotest,whatnottotest(OutofScope)
TestObjectives whytest
Assumptions whatweknowordontknowaboutUAT
RiskAnalysis whathappenifwedonttest
TestDesign scenariosandtestcases
Roles&Responsibilities whoistodowhat
TestSchedule&Resources time,milestone(checkpoint)
TestDataManagement whatresourcesandinfrastructures
TestEnvironment machines,databases
CommunicationApproach sharinginfoordoccenter
TestTools testmanagementtoolorfunctiontestingtool
ExitCriteria whentostoptesting
10
Howtowriteatestplan
HowtoWriteaTestPlanDocument
SampleTestPlanDocumentforOrangeHRM
Project
GenericTestPlan NPUWebPage
11
TestStrategy
Ateststrategyisanoutlinethatdescribesthetesting
portionofthesoftwaredevelopmentcycle.Itiscreatedto
informprojectmanagers,testers,anddevelopersabout
somekeyissuesofthetestingprocess.Thisincludesthe
testingobjective,methodsoftestingnewfunctions,total
timeandresourcesrequiredfortheproject,andthetesting
environment.
Theteststrategydescribeshowtheproductrisksofthe
stakeholdersaremitigatedatthetestlevel,whichtypesof
testaretobeperformed,andwhichentryandexitcriteria
apply.(source:Wikipedia)
Theteststrategyiscreatedbasedondevelopmentdesign
documents.ItiswrittenbytheTestManagerorLead.
12
TestStrategy
ThefollowingaresomeofthecomponentsthattheTestStrategy
includes:
1TestLevels.
2RolesandResponsibilities.
3EnvironmentRequirements.
4TestingTools.
5RisksandMitigation.
6TestSchedule.
7RegressionTestApproach.
8TestGroups.
9TestPriorities.
10TestStatusCollectionsandReporting.
11TestRecordsMaintenance.
12Requirementstraceabilitymatrix.
13TestSummary
CheckhowtheTestStrategylookslike inWWW.
13
TraceabilityMatrix isamethodusedtovalidatethe
complianceofproductwithrequirementsforthat
product.Therequirementiswritteninarowofthe
matrixandthecolumnsofthematrix.
Itisusedtocrosscheckthetestcasesasperthe
requirementofthetestcases. Inotherwords,it
checkswhethertheeachfunctionalityiscoveredin
theTestCasesasperrequirementdocument. (We
createRTMusingQualityCentertool)
Howtocreaterequirementstestmatrixtemplate
14
Exercise
1. ReadTextBookChapter3.23.7
2. ReadAppendixA(TestPlanAccordingtoIEEE
Standard8291998)
15
SelfcheckQuestions
1. HaveyouwrittenTestPlan?WhatisaTest
Plan?Whatdoesitinclude?
2. Whatarethedifferencesbetweentest
strategyandtestplan?
3. Howdoyouprioritizetestingtaskswithina
project?
4. WhatisTraceabilityMatrix?Howtocreate
Template?
16
SelfcheckQuestions
5.WhatarethedimensionsoftheRisks?
6.Whatifthereisntenoughtimeforthorough
testing?
7.Whatarethefactorsresponsibleforthe
estimationofsystemintegrationtestcycleand
totalintegrationtime?
8.WhatisChangeControl(ORChange
Request)?
17
Assignment(Homework)
HW3
Createaneffectivetestplanforafeature
choosingfromfollowingdomains
(1)ECommerce Amazon,eBay,TOYOTA
(2)Financials BankofAmerica
(3)InternetServiceProvider Yahoo,Google
(4)SocialMedia Facebook,LinkedIn,Twitter
(5)CloudComputing Salesforce
(6)HealthCare CoveredCalifornia
18
Assignment(Homework)
HW3
Thetestplanshouldchoosefiveormore
componentsfrom:
TestScope,OutofScope,TestObjectives,Assumptions,
RiskAnalysis,TestDesign,Roles&Responsibilities,Test
Schedule&Resources,TestDataManagement,Test
Environment,CommunicationApproach,TestTools,Exit
Criteria.
http://www.softwaretestinghelp.com/howtowritetest
plandocumentsoftwaretestingtrainingday3/
19
SampleTestPlanOrangeHRMLiveProjectTrainingwww.SoftwareTestingHelp.com
www.SoftwareTestingHelp.com

Test Plan (a Real Sample)
SoftwareTestingHelp.com Live Project Training OrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveprojectfor
trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject
Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsignoff)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
Description of Change
02/14/2014
Swati Seela
Draft
02/14/2014
Vijay Shinde
Draft - Reviewed
ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Approver/
Reviewer
Role
Approval/
ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
1.0
DocumentName
ORANGEHRMVERSION3.0 MYINFOMODULE FSD
CompanyconfidentialPage1
Table of Contents
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
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
1. INTRODUCTION
1.1. Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject(e.g.:start/end
dates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest(e.g.:entry/exit
criteria,creationoftestcases,specifictaskstoperform,scheduling,datastrategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocesstoidentifyandreport
defects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthatcomeupduring
execution(e.g.:communications,escalationprocedures,riskandmitigation,teamroster)
1.2. Project Overview

MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoviewrelevant
informationsuchaspersonalinformationandupdatingpersonalinformationwithaninternetenabled
PCwithouthavingtoinvolvetheHRdepartment.
The functionality of this module spans through the entire system, making information available
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,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,approvesthe
documentandisaccountablefortheresults.
The stakeholders representatives and participants (individuals as identified by the PMO Leads)
maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsofthetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththedesign,providesthe
environmentfortestingandfollowstheproceduresrelatedtothefixesofdefects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
2. TEST STRATEGY
2.1. Test Objectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtestexecution.
2.2. Test Assumptions

KeyAssumptions
ProductionlikedatarequiredandbeavailableinthesystempriortostartofFunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPNconnectivity
The Test Team assumes all necessary inputs required during Test design and execution will be
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.
The system will be treated as a black box; if the information shows correctly online and in the
reports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.
FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailableonthesystemat
thetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRMVERSION3.0MYINFO
MODULE
UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQAGroupwillprovidetheir
supportoncreatingUATscript.
2.3. Test Principles
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,andquality.
Therewillbecommon,consistentproceduresforallteamssupportingtestingactivities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeasneeded.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyorduplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchaspossible.
Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectivesandgoals.
Therewillbeentranceandexitcriteria.
2.4. Data Approach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwillcontainpreloadedtestdata
andwhichisusedfortestingactivities.
2.5. Scope and Levels of Testing

2.5.1.
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbeforethenext
levelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytestscriptsand
documentation
TIMING:atthebeginningofeachcycle.
2.5.2.
Functional Test
PURPOSE: Functional testing will be performed to check the functions of application. The
functional testing is carried out by feeding the input and validates the output from the
application.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:Thescopeis
highlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeenembeddedas
separatedocument.Ifyoupreferyoucaninsertatablehereitself.Thescopeiscreatedbased
ontheTestscenariosthatwereidentifiedinthepreviousarticle.
Functional Testing
Scope.xlsx
TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whicharestoredinHP
ALM.
TIMING:afterExploratorytestiscompleted.
TESTACCEPTANCECRITERIA
1. ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbeavailable
priortostartofTestdesignphase.
2. TestcasesapprovedandsignedoffpriortostartofTestexecution
3. Developmentcompleted,unittestedwithpassstatusandresultssharedtoTestingteam
toavoidduplicatedefects
4. Testenvironmentwithapplicationinstalled,configuredandreadytousestate
Signoff
ApprovedFunctionalSpecificationDocument
ApprovedUsecases
ApprovedTestcases
Readiness
Developmentcompleted&unittested
Applicationdeployedandsystemreadyfor
testingonTestenvironment
Productionlikedataisavailabletotestall
functionalities.
DefectfixesplannedbasedonDefecttriage
(UnitTesting)andevaluationcriteria
TESTDELIVERABLES
S.No.
DeliverableName
1.
TestPlan
2.
FunctionalTestCases
3.
LoggingDefectsinHPALM
(4.
Daily/weeklystatusreport
5.
TestClosurereport
Author
TestLead
Reviewer
Project
Manager/
BusinessAnalysts
TestTeam
Business
Analysts
Signoff
TestTeam
Test
Lead/
Programming
Lead(Vijay)
TestTeam/TestLead Test Lead/ Project
Manager
TestLead
ProjectManager
MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons
a) AnyissuesintheSystemenvironmentreadiness
b) Anychangeinscope/additioninscope
c) Anyotherdependencythatimpactseffortsandtimelines
Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,wecan
estimatehowmuchtimeittakesandestablishthetimelinesasyoucanseeinthebelow
embeddedexcelsheet.
DFRT Execution
Cycle.xlsx
2.5.3.
User Acceptance Test (UAT)

PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheenduserstocomplete
onefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaroundbusiness
needsandhowthesystemadaptstothem,itmayhappenthattheusersdosomevalidation
notcontainedinthescripts.TestteamwritetheUATtestcasesbasedontheinputsfromEnd
user(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Onlyafterthis
testiscompletedtheproductcanbereleasedtoproduction.
TESTDELIVERABLES
S.No.
DeliverableName
1.
UATTestCases
Author
TestTeam
Reviewer
Business
Analysts
Signoff
2.6. Test Effort Estimate

ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.
3.
New_Detailed DRFT
Test estimate v1.xlsx
Note:thisestimateisfortheTCOEteamonlyTestingSchedule
4. EXECUTION STRATEGY
4.1. Entry and Exit Criteria
The entry criteria refer to the desirable conditions in order to start test execution; only the
migrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
The exit criteria are the desirable conditions that need to be met in order proceed with the
implementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteamwillassessthe
risk, identify mitigation actions and provide a recommendation. All this is input to the project
managerforafinalgonogodecision.
Entry criteria to start the execution phase of the test: the activities listed in the Test Planning
sectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsectionoftheschedule
are100%completedateachcycle.
Test
Team
ExitCriteria
Technical
Team
100%TestScriptsexecuted
95%passrateofTestScripts
NoopenCriticalandHighseveritydefects
95%ofMediumseveritydefectshavebeenclosed
Notes
Allremainingdefectsareeithercancelledor
documentedasChangeRequestsforafuture
release
Allexpectedandactualresultsarecapturedand
documentedwiththetestscript
AlltestmetricscollectedbasedonreportsfromHP
ALM
AlldefectsloggedinHPALM
TestClosureMemocompletedandsignedoff
Testenvironmentcleanupcompletedandanew
backupoftheenvironment
4.2. Test Cycles

Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteallthescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,andmostofthehigh
defects.Itisexpectedtousesomeworkaroundinordertogettoallthescripts.
o Theobjectiveofthesecondcycleistoidentifyremaininghighandmediumdefects,remove
the workaround from the first cycle, correct gaps in the scripts and obtain performance
results.
UATtestwillconsistofonecycle.
o
o
4.3. Validation and Defect Management
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribedabove.However
itisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifyapossiblegapinthe
scripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusinessanalystsjointheTCOEin
theexecutionofthetest,sincetheBUSINESSANALYSTshaveadeeperknowledgeofthebusiness
processes.Ifagapisidentified,thescriptsandtraceabilitymatrixwillbeupdatedandthenadefect
loggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgatherinformationona
dailybasisfromHPALM,andrequestadditionaldetailsfromtheDefectCoordinator.Thetechnical
teamwillworkonfixes.
It is the responsibility of the tester to open the defects, link them to the corresponding script,
assignaninitialseverityandstatus,retestandclosethedefect;itistheresponsibilityoftheDefect
Managertoreviewtheseverityofthedefectsandfacilitatewiththetechnicalteamthefixandits
implementation,communicatewithtesterswhenthetestcancontinueorshouldbehalt,request
the tester to retest, and modify status as the defect progresses through the cycle; it is the
responsibilityofthetechnicalteamtoreviewHPALMonadailybasis,askfordetailsifnecessary,
fixthedefect,communicatetotheDefectManagerthefixisdone,implementthesolutionperthe
DefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
1(Critical)
Impact
2(High)
3(Medium)
4(Low)
5(Cosmetic)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,or
causepotentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystem
failuremessageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
Itcausesalackofvitalprogramfunctionalitywithworkaround.
ThisBugwilldegradethequalityoftheSystem.Howeverthereisan
intelligent workaround for achieving the desired functionality for
examplethroughanotherscreen.
This bug prevents other areas of the product from being tested.
Howeverotherareascanbeindependentlytested.
Thereisaninsufficientorunclearerrormessage,whichhasminimum
impactonproductuse.
Thereisaninsufficientorunclearerrormessagethathasnoimpacton
productuse.
4.4. Test Metrics

Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.Thebelowaresomeofthemetrics
Report
Description
Frequency
Test
preparation
&
Execution
Status
Toreporton%complete,%WIP,%Pass,%Fail
Daily
execution
ToreportonPass,Fail,Totaldefects,highlight
Showstopper/Criticaldefects
Daily
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfproject
teamneedsweekly
DefectsseveritywiseStatusOpen,closed,anyother
Status
Weekly/Daily
(optional)
status
Project
Weekly
Status
report
updateapartfrom
dailyandthereis
templateavailable
withprojectteamto
use.
4.5. Defect tracking & Reporting

FollowingflowchartdepictsDefectTrackingProcess:
Start
Tester:
Test
Lead
Dev
Lead
Develo
per:
Tester:
R t t
N
Appr
Y
Cl
Stop
5. TEST MANAGEMENT PROCESS
5.1.
TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltestingartifacts
suchasTestcases,testresultsareupdatedintheHPApplicationLifecycleManagement(ALM)
tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatusofthisDFRT
project.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccesstoadd/modify
TestcasesinHPALM.
5.2.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.Anychangeto
thetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethestatusof
eachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTestcase/test
step.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythedefectfix.
ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTestexecution.For
example,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopendefects,Severity
wisedefectsetc.
TestDesignProcess
Understanding
Requirements
Establishing
Traceability
MatrixinHP
ALM
Preparationof
Testcases
SME/Peer
ReviewofTest
cases
Incorporating
Review
commentsin
testcases
Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartofTraceability
matrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthereview
defectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbesharedperiodically
withtheRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailing
implicitrequirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusinessAnalysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHPALM.
5.3.
TestExecutionProcess
Executeeachof
theteststepin
testcase
MarkStatusas
Pass/FailinHP
ALM
Raisedefectsfor
thefailedtest
casesinHPALM
Sendthedaily
statusreportto
TestLead
Participatein
DefectTriage
cycleandexplain
thedefects
Completethe
testexecutionof
allthetestcases
OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,tester
willstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefor
testing.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMforupdating
teststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtooldetailing
stepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoallstakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltestcases
areexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaselevelorat
thespecificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresultswillbe
updatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
5.4. Test Risks and Mitigation Factors
Risk
SCHEDULE
Prob.
High
Impact
High
Mitigation Plan
Thetestingteamcancontrolthe
preparationtasks(inadvance)
Risk
Prob.
Impact
Testingscheduleistight.Ifthestart
ofthetestingisdelayeddueto
designtasks,thetestcannotbe
extendedbeyondtheUAT
scheduledstartdate.
RESOURCES
Notenoughresources,resourceson
boardingtoolate(processtakes
around15days.
DEFECTS
Defectsarefoundatalatestageof
thecycleoratalatecycle;defects
discoveredlatearemostlikelybe
duetounclearspecificationsand
aretimeconsumingtoresolve.
SCOPE
Scopecompletelydefined
Medium
High
Medium
High
Medium
Medium
Low
Medium
Medium
High
Medium
High
Naturaldisasters
NonavailabilityofIndependentTest
environmentandaccessibility
DelayedTestingDueTonewIssues
Mitigation Plan
andtheearlycommunication
withinvolvedparties.
Somebufferhasbeenaddedto
thescheduleforcontingencies,
althoughnotasmuchasbest
practicesadvise.
Holidaysandvacationhavebeen
estimatedandbuiltintothe
schedule;deviationsfromthe
estimationcouldderiveindelaysin
thetesting.
Defectmanagementplanisinplace
toensurepromptcommunication
andfixingofissues.
Scopeiswelldefinedbutthe
changesareinthefunctionalityare
notyetfinalizedorkeepon
changing.
Teamsandresponsibilitieshave
beenspreadtotwodifferent
geographicareas.Inacatastrophic
eventinoneoftheareas,therewill
resourcesintheotherareasneeded
tocontinue(althoughataslower
pace)thetestingactivities.
Duetononavailabilityofthe
environment,theschedulegets
impactedandwillleadtodelayed
startofTestexecution.
Duringtesting,thereisagood
chancethatsomenewdefects
maybeidentifiedandmaybecome
anissuethatwilltaketimeto
resolve.
Therearedefectsthatcanberaised
duringtestingbecauseofunclear
documentspecification.These
defectscanyieldtoanissuethatwill
needtimetoberesolved.
Risk
Prob.
Impact
Mitigation Plan
Iftheseissuesbecome
showstoppers,itwillgreatlyimpact
ontheoverallprojectschedule.
Ifnewdefectsarediscovered,the
defectmanagementandissue
managementproceduresarein
placetoimmediatelyprovidea
resolution.
5.1. Communications Plan and Team Roster

5.2. Role Expectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
Roles
5.2.1.
1.
ProjectManager
2.
TestLead
3.
BusinessAnalyst
4.
DevelopmentLead
5.
TestingTeam
6.
DevelopmentTeam
7.
TechnicalLead
ContactInfo
Project Management
5.2.2.
Name
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTestEstimates
signsoffonit.
Test Planning (Test Lead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expectedresults
andexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
5.2.3.
Communicatetothetestteamanychangesthatneedtobemadetothetestdeliverables
orapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Provide functional (Business Analysts) and technical team to test team personnel (if
needed).
Test Team
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedbytheTest
lead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
5.2.4. Test Lead
5.2.5.
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitate defect communications between testing team and technical / development
team.
Development Team
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)andprovide
timelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthepoints
specifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydateslipsbased
onthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationofcomponents.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttestexecutorsin
creationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
6. TEST ENVIRONMENT
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.
Awindowsenvironmentwith Internet 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 live
projecttrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

LInkedin Test Plan

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LInkedin Test Plan

Uploaded by

Copyright:

Available Formats

Week#3

SoftwareTestingHelp.com Live Project Training OrangeHRM

1.2. Project Overview

2.2. Test Assumptions

2.3. Test Principles

2.4. Data Approach

2.5. Scope and Levels of Testing

User Acceptance Test (UAT)

2.6. Test Effort Estimate

4.2. Test Cycles

4.3. Validation and Defect Management

4.4. Test Metrics

4.5. Defect tracking & Reporting

5. TEST MANAGEMENT PROCESS

5.4. Test Risks and Mitigation Factors

5.1. Communications Plan and Team Roster

Test Planning (Test Lead)

5.2.4. Test Lead

You might also like