7.

TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.
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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject
trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject
Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

ingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.
4(Low)
Thereisaninsufficientorunclearerrormessage,whichhasminimumimpacton
productuse.
5(Cosmetic)

Thereisaninsufficientorunclearerrormessagethathasnoimpactonproduct
use.

TestMetrics
Testmetricstomeasuretheprogressandlevelofsuccessofthetestwillbedevelopedandsharedwith
theprojectmanagerforapproval.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
ProjectWeeklyStatusreport
Projectdrivenreporting(AsrequestedbyPM)
WeeklyIfprojectteamneedsweeklyupdateapartfromdailyandthereistemplateavailablewith
projectteamtouse.

Defecttracking&Reporting
FollowingflowchartdepictsDefectTrackingProcess:
TESTMANAGEMENTPROCESS

TestManagementTool
HPApplicationLifecycleManagementisthetoolusedforTestManagement.Alltesting
artifactssuchasTestcases,testresultsareupdatedintheHPApplicationLifecycle
Management(ALM)tool.
ProjectspecificfolderstructurewillbecreatedinHPALMtomanagethestatus
ofthisDFRTproject.
EachresourceintheTestingteamwillbeprovidedwithRead/Writeaccessto
add/modifyTestcasesinHPALM.
DuringtheTestDesignphase,alltestcasesarewrittendirectlyintoHPALM.
AnychangetothetestcasewillbedirectlyupdatedintheHPALM.
EachTesterwilldirectlyaccesstheirrespectiveassignedtestcasesandupdatethe
statusofeachexecutedstepinHPALMdirectly.
AnydefectencounteredwillberaisedinHPALMlinkingtotheparticularTest
case/teststep.
DuringDefectfixtesting,defectsarereassignedbacktothetestertoverifythe
defectfix.ThetesterverifiesthedefectfixandupdatesthestatusdirectlyinHPALM.
VariousreportscanbegeneratedfromHPALMtoprovidestatusofTest
execution.Forexample,StatusreportofTestcasesexecuted,Passed,Failed,No.ofopen
defects,Severitywisedefectsetc.
TestDesignProcess

Thetesterwillunderstandeachrequirementandpreparecorrespondingtestcaseto
ensureallrequirementsarecovered.
EachTestcasewillbemappedtoUsecasestoRequirementsaspartof
Traceabilitymatrix.
EachoftheTestcaseswillundergoreviewbytheBUSINESSANALYSTandthe
reviewdefectsarecapturedandsharedtotheTestteam.Thetesterswillreworkonthereview
defectsandfinallyobtainapprovalandsignoff.
Duringthepreparationphase,testerwillusetheprototype,usecaseandfunctional
specificationtowritestepbysteptestcases.
TesterswillmaintainaclarificationTrackersheetandsamewillbeshared
periodicallywiththeRequirementsteamandaccordinglythetestcasewillbeupdated.The
clarificationsmaysometimesleadtoChangeRequestsornotinscopeordetailingimplicit
requirements.
SignoffforthetestcaseswouldbecommunicatesthroughmailbyBusiness
Analysts.
AnysubsequentchangestothetestcaseifanywillbedirectlyupdatedinHP
ALM.
TestExecutionProcess

OnceallTestcasesareapprovedandthetestenvironmentisreadyfortesting,
testerwillstartaexploratorytestoftheapplicationtoensuretheapplicationisstablefortesting.
EachTesterisassignedTestcasesdirectlyinHPALM.
Testerstoensurenecessaryaccesstothetestingenvironment,HPALMfor
updatingteststatusandraisedefects.Ifanyissues,willbeescalatedtotheTestLeadandinturn
 totheProjectManagerasescalation.
Ifanyshowstopperduringexploratorytestingwillbeescalatedtotherespective
developmentSPOCsforfixes.
Eachtesterperformsstepbystepexecutionandupdatestheexecutionsstatus.The
testerentersPassorFailStatusforeachofthestepdirectlyinHPALM.
TesterwillprepareaRunchartwithdaywiseexecutiondetails
Ifanyfailures,defectwillberaisedasperseverityguidelinesinHPALMtool
detailingstepstosimulatealongwithscreenshotsifappropriate.
DailyTestexecutionstatusaswellasDefectstatuswillbereportedtoall
stakeholders.
Testingteamwillparticipateindefecttriagemeetingsinordertoensurealltest
casesareexecutedwitheitherpass/failcategory.
Ifthereareanydefectsthatarenotpartofstepsbutcouldbeoutsidetheteststeps,
suchdefectsneedtobecapturedinHPALMandmapitagainstthetestcaseleveloratthe
specificstepthatissuewasencounteredafterconfirmingwithTestLead.
ThisprocessisrepeateduntilalltestcasesareexecutedfullywithPass/Failstatus.
Duringthesubsequentcycle,anydefectsfixedappliedwillbetestedandresults
willbeupdatedinHPALMduringthecycle.
AsperProcess,finalsignofforprojectcompletionprocesswillbefollowed
TestRisksandMitigationFactors
Risk
Prob.
Impact
MitigationPlan
SCHEDULE
Testingscheduleistight.Ifthestartofthetestingisdelayedduetodesigntasks,thetestcannotbe
extendedbeyondtheUATscheduledstartdate.
High
High
Thetestingteamcancontrolthepreparationtasks(inadvance)andtheearly
communicationwithinvolvedparties.
Somebufferhasbeenaddedtothescheduleforcontingencies,althoughnotas
muchasbestpracticesadvise.
RESOURCES
Notenoughresources,resourcesonboardingtoolate(processtakesaround15days.

Medium
High
Holidaysandvacationhavebeenestimatedandbuiltintotheschedule;deviationsfromtheestimation
couldderiveindelaysinthetesting.
DEFECTS
Defectsarefoundatalatestageofthecycleoratalatecycle;defectsdiscoveredlatearemostlikelybe
duetounclearspecificationsandaretimeconsumingtoresolve.

Medium
High
Defectmanagementplanisinplacetoensurepromptcommunicationandfixingofissues.
SCOPE
Scopecompletelydefined

Medium
Medium
Scopeiswelldefinedbutthechangesareinthefunctionalityarenotyetfinalizedorkeeponchanging.
Naturaldisasters
Low
Medium
Teamsandresponsibilitieshavebeenspreadtotwodifferentgeographicareas.Inacatastrophiceventin
oneoftheareas,therewillresourcesintheotherareasneededtocontinue(althoughataslowerpace)
thetestingactivities.
NonavailabilityofIndependentTestenvironmentandaccessibility
Medium
High
Duetononavailabilityoftheenvironment,theschedulegetsimpactedandwillleadtodelayedstartof
Testexecution.
DelayedTestingDueTonewIssues
Medium
High
Duringtesting,thereisagoodchancethatsomenewdefectsmaybeidentifiedandmaybecomean
issuethatwilltaketimetoresolve.
Therearedefectsthatcanberaisedduringtestingbecauseofuncleardocumentspecification.These
defectscanyieldtoanissuethatwillneedtimetoberesolved.
Iftheseissuesbecomeshowstoppers,itwillgreatlyimpactontheoverallprojectschedule.
Ifnewdefectsarediscovered,thedefectmanagementandissuemanagementproceduresareinplaceto
immediatelyprovidearesolution.
CommunicationsPlanandTeamRoster
RoleExpectations
Thefollowinglistdefinesingeneraltermstheexpectationsrelatedtotherolesdirectlyinvolvedinthe
management,planningorexecutionofthetestfortheproject.
SN0.
Roles
Name
ContactInfo
1.
ProjectManager

2.
TestLead

3.
BusinessAnalyst

4.
DevelopmentLead
5.
TestingTeam

6.
DevelopmentTeam

7.
TechnicalLead

ProjectManagement
ProjectManager:reviewsthecontentoftheTestPlan,TestStrategyandTest
Estimatessignsoffonit.
TestPlanning(TestLead)
Ensureentrancecriteriaareusedasinputbeforestarttheexecution.
Developtestplanandtheguidelinestocreatetestconditions,testcases,expected
resultsandexecutionscripts.
Provideguidelinesonhowtomanagedefects.
Attendstatusmeetingsinpersonorviatheconferencecallline.
Communicatetothetestteamanychangesthatneedtobemadetothetest
deliverablesorapplicationandwhentheywillbecompleted.
Provideonpremiseortelecommutesupport.
Providefunctional(BusinessAnalysts)andtechnicalteamtotestteampersonnel
(ifneeded).
TestTeam
Developtestconditions,testcases,expectedresults,andexecutionscripts.
Performexecutionandvalidation.
Identify,documentandprioritizedefectsaccordingtotheguidanceprovidedby
theTestlead.
Retestaftersoftwaremodificationshavebeenmadeaccordingtotheschedule.
Preparetestingmetricsandprovideregularstatus.
TestLead
Acknowledgethecompletionofasectionwithinacycle.
GivetheOKtostartnextleveloftesting.
Facilitatedefectcommunicationsbetweentestingteamandtechnical/
developmentteam.
DevelopmentTeam
Reviewtestingdeliverables(testplan,cases,scripts,expectedresults,etc.)and
providetimelyfeedback.
Assistinthevalidationofresults(ifrequested).
Supportthedevelopmentandtestingprocessesbeingusedtosupporttheproject.
Certifycorrectcomponentshavebeendeliveredtothetestenvironmentatthe
pointsspecifiedinthetestingschedule.
Keepprojectteamandleadershipinformedofpotentialsoftwaredeliverydate
slipsbasedonthecurrentschedule.
Defineprocesses/toolstofacilitatetheinitialandongoingmigrationof
components.
Conductfirstlineinvestigationintoexecutiondiscrepanciesandassisttest
 executorsincreationofaccuratedefects.
Implementfixestodefectsaccordingtoschedule.
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.

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.

APPROVALS

TheNamesandTitlesofallpersonswhomustapprovethisplan.
Signature:

Name:

Role:

Date:

Signature:

Name:

Role:

Date:

Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

trainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

TestPlan(aRealSample)
SoftwareTestingHelp.comLiveProjectTrainingOrangeHRM

2/1/2014
SoftwareTestingHelp.com
Nameofthetester
Note:Thisisasampletestplancreatedonrealtimesoftwaretestingliveproject

fortrainingconductedbysoftwaretestinghelp.comonfollowingpage:
=>ClickhereforSoftwareTestingFreeTrainingonaLiveProject

Version:1.0
Created:02/05/2014
LastUpdated:02/05/2014
Status:DRAFT(ThestatuswouldchangetofinalizedposttheBA,PManddevteamreviewandsign
off)
RevisionandSignoffSheet
DocumentHistoryTomaintainalistofchangesbeingmade
Version
Date
Author
DescriptionofChange
1
02/14/2014
SwatiSeela
Draft
2
02/14/2014
VijayShinde
DraftReviewed

ApproversListTotrackwhohasreviewedandsignoffontheTestplan
Name
Role
Approver/Reviewer
Approval/ReviewDate
ReferenceDocumentsClearlymarkthedocumentusedasaninputtocreatethetestplan
Version
Date
Document Name
1.0

ORANGEHRM VERSION 3.0 MY INFO MODULE -FSD

TableofContents

1. INTRODUCTION 5
1.1. Purpose 5
1.2. ProjectOverview 5
1.3. Audience 5
2. TESTSTRATEGY 5
2.1. TestObjectives 5
2.2. TestAssumptions 6
2.3. TestPrinciples 7
2.4. DataApproach 7
2.5. ScopeandLevelsofTesting 7
2.5.1. Exploratory 7
2.5.2. FunctionalTest 8
TESTACCEPTANCECRITERIA 8
TESTDELIVERABLES 8
MILESTONELIST 9
2.5.3. UserAcceptanceTest(UAT)9
TESTDELIVERABLES 9
2.6. TestEffortEstimate 10
3. EXECUTIONSTRATEGY 10
3.1. EntryandExitCriteria 10
3.2. TestCycles 11
3.3. ValidationandDefectManagement 11
3.4. TestMetrics 12
3.5. Defecttracking&Reporting 13
4. TESTMANAGEMENTPROCESS 13
4.1. TestManagementTool 13
4.2. TestDesignProcess 14
4.3. TestExecutionProcess 15
4.4. TestRisksandMitigationFactors 16
4.1. CommunicationsPlanandTeamRoster 17
4.2. RoleExpectations 17
4.2.1. ProjectManagement 18
4.2.2. TestPlanning(TestLead) 18
4.2.3. TestTeam 18
4.2.4. TestLead 18
4.2.5. DevelopmentTeam 18
5. TESTENVIRONMENT 19
INTRODUCTION
Purpose
Thistestplandescribesthetestingapproachandoverallframeworkthatwilldrivethetestingofthe
OrangeHRMVersion3.0MyInfoModule.comsite.Thedocumentintroduces:
TestStrategy:rulesthetestwillbebasedon,includingthegivensoftheproject
(e.g.:start/enddates,objectives,assumptions);descriptionoftheprocesstosetupavalidtest
(e.g.:entry/exitcriteria,creationoftestcases,specifictaskstoperform,scheduling,data
strategy).
ExecutionStrategy:describeshowthetestwillbeperformedandprocessto
identifyandreportdefects,andtofixandimplementfixes.
TestManagement:processtohandlethelogisticsofthetestandalltheeventsthat
comeupduringexecution(e.g.:communications,escalationprocedures,riskandmitigation,
teamroster)
ProjectOverview
MyInfoModuleisapowerfultoolprovidingemployeesofthecompanywiththeabilitytoview
relevantinformationsuchaspersonalinformationandupdatingpersonalinformationwithaninternet
enabledPCwithouthavingtoinvolvetheHRdepartment.
Thefunctionalityofthismodulespansthroughtheentiresystem,makinginformationavailable
anywhere,anytime.Allinformationissubjecttocompanysdefinedsecuritypolicy,wherehe/shecan
onlyviewtheinformationhe/sheisauthorizedto.AnESSUsercanonlyeditcertainfieldsintheESS
Module,maintainingthesecurityandconfidentialityofemployeeinformation
Audience
Projectteammembersperformtasksspecifiedinthisdocument,andprovideinput
andrecommendationsonthisdocument.
ProjectManagerPlansforthetestingactivitiesintheoverallprojectschedule,
reviewsthedocument,trackstheperformanceofthetestaccordingtothetaskhereinspecified,
approvesthedocumentandisaccountablefortheresults.
Thestakeholdersrepresentativesandparticipants(individualsasidentifiedbythe
PMOLeads)maytakepartintheUATtesttoensurethebusinessisalignedwiththeresultsof
thetest.
TechnicalTeamensuresthatthetestplananddeliverablesareinlinewiththe
design,providestheenvironmentfortestingandfollowstheproceduresrelatedtothefixesof
defects.
Businessanalystswillprovidetheirinputsonfunctionalchanges.
TESTSTRATEGY
TestObjectives
TheobjectiveofthetestistoverifythatthefunctionalityofORANGEHRMVERSION3.0MYINFO
MODULEworksaccordingtothespecifications.
Thetestwillexecuteandverifythetestscripts,identify,fixandretestallhighandmediumseverity
defectspertheentrancecriteria,prioritizelowerseveritydefectsforfuturefixingviaCR.
Thefinalproductofthetestistwofold:
Aproductionreadysoftware;
AsetofstabletestscriptsthatcanbereusedforFunctionalandUATtest
execution.
TestAssumptions
KeyAssumptions
Productionlikedatarequiredandbeavailableinthesystempriortostartof
FunctionalTesting
Ineachtestingphase,Cycle3willbeinitiatedifthedefectrateishighinCycle2.
General
ExploratoryTestingwouldbecarriedoutoncethebuildisreadyfortesting
Performancetestingisnotconsideredforthisestimation.
AllthedefectswouldcomealongwithasnapshotJPEGformat
TheTestTeamwillbeprovidedwithaccesstoTestenvironmentviaVPN
connectivity
TheTestTeamassumesallnecessaryinputsrequiredduringTestdesignand
executionwillbesupportedbyDevelopment/BUSINESSANALYSTsappropriately.
TestcasedesignactivitieswillbeperformedbyQAGroup
TestenvironmentandpreparationactivitieswillbeownedbyDevTeam
DevteamwillprovideDefectfixplansbasedontheDefectmeetingsduringeach
cycletoplan.ThesamewillbeinformedtoTestteampriortostartofDefectfixcycles
BUSINESSANALYSTwillreviewandsignoffallTestcasespreparedbyTest
TeampriortostartofTestexecution
ThedefectswillbetrackedthroughHPALMonly.Anydefectfixesplannedwill
besharedwithTestTeampriortoapplyingthefixesontheTestenvironment
ProjectManager/BUSINESSANALYSTwillreviewandsignoffalltest
deliverables
Theprojectwillprovidetestplanning,testdesignandtestexecutionsupport
TestteamwillmanagethetestingeffortwithclosecoordinationwithProject
PM/BUSINESSANALYST
Projectteamhastheknowledgeandexperiencenecessary,orhasreceived
adequatetraininginthesystem,theprojectandthetestingprocesses.
Thereisnoenvironmentdowntimeduringtestduetooutagesordefectfixes.
Thesystemwillbetreatedasablackbox;iftheinformationshowscorrectly
onlineandinthereports,itwillbeassumedthatthedatabaseisworkingproperly.
Cycle3willbeinitiatediftherearemoredefectsinCycle2.

FunctionalTesting
DuringFunctionaltesting,testingteamwillusepreloadeddatawhichisavailable
onthesystematthetimeofexecution
TheTestTeamwillbeperformFunctionaltestingonlyonORANGEHRM
VERSION3.0MYINFOMODULE

UAT
UATtestexecutionwillbeperformedbyendusers(L1,L2andL3)andQA
GroupwillprovidetheirsupportoncreatingUATscript.

TestPrinciples
Testingwillbefocusedonmeetingthebusinessobjectives,costefficiency,and
quality.
Therewillbecommon,consistentproceduresforallteamssupportingtesting
activities.
Testingprocesseswillbewelldefined,yetflexible,withtheabilitytochangeas
needed.
Testingactivitieswillbuilduponpreviousstagestoavoidredundancyor
duplicationofeffort.
Testingenvironmentanddatawillemulateaproductionenvironmentasmuchas
possible.
 Testingwillbearepeatable,quantifiable,andmeasurableactivity.
Testingwillbedividedintodistinctphases,eachwithclearlydefinedobjectives
andgoals.
Therewillbeentranceandexitcriteria.
DataApproach
Infunctionaltesting,ORANGEHRMVERSION3.0MYINFOMODULEwill
containpreloadedtestdataandwhichisusedfortestingactivities.
ScopeandLevelsofTesting
Exploratory
PURPOSE:thepurposeofthistestistomakesurecriticaldefectsareremovedbefore
thenextlevelsoftestingcanstart.
SCOPE:Firstlevelnavigation,dealerandadminmodules
TESTERS:Testingteam.
METHOD:thisexploratorytestingiscarriedoutintheapplicationwithoutanytest
scriptsanddocumentation
TIMING:atthebeginningofeachcycle.
FunctionalTest
PURPOSE:Functionaltestingwillbeperformedtocheckthefunctionsof
application.Thefunctionaltestingiscarriedoutbyfeedingtheinputandvalidatesthe
outputfromtheapplication.
Scope:ThebelowexcelsheetdetailsaboutthescopeofFunctionaltest.Note:The
scopeishighlevelduetochangesintherequirement.
Tokeepthedocumenteasilyfragmentedandcategorized,thescopehasbeen
embeddedasseparatedocument.Ifyoupreferyoucaninsertatablehereitself.The
scopeiscreatedbasedontheTestscenariosthatwereidentifiedinthepreviousarticle.

TESTERS:TestingTeam.
METHOD:ThetestwillbeperformedaccordingtoFunctionalscripts,whichare
storedinHPALM.
TIMING:afterExploratorytestiscompleted.

TESTACCEPTANCECRITERIA
ApprovedFunctionalSpecificationdocument,Usecasedocumentsmustbe
availablepriortostartofTestdesignphase.
TestcasesapprovedandsignedoffpriortostartofTestexecution
Developmentcompleted,unittestedwithpassstatusandresultssharedtoTesting
teamtoavoidduplicatedefects
Testenvironmentwithapplicationinstalled,configuredandreadytousestate

TESTDELIVERABLES

S.No.
DeliverableName
Author
Reviewer
1.
TestPlan
TestLead
ProjectManager/BusinessAnalysts
2.
FunctionalTestCases
TestTeam
BusinessAnalystsSignoff
3.
LoggingDefectsinHPALM
TestTeam
TestLead/ProgrammingLead(Vijay)
(4.
Daily/weeklystatusreport
TestTeam/TestLead
TestLead/ProjectManager
5.
TestClosurereport
TestLead
ProjectManager

MILESTONELIST
Themilestonelististentativeandmaychangeduetobelowreasons

AnyissuesintheSystemenvironmentreadiness
Anychangeinscope/additioninscope
Anyotherdependencythatimpactseffortsandtimelines

Testinggenerallyisnotcarriedoutinonecycle.Basedonthetestingscope,we
canestimatehowmuchtimeittakesandestablishthetimelinesasyoucanseein
thebelowembeddedexcelsheet.

UserAcceptanceTest(UAT)
PURPOSE:thistestfocusesonvalidatingthebusinesslogic.Itallowstheendusersto
completeonefinalreviewofthesystempriortodeployment.
TESTERS:theUATisperformedbytheendusers(L1,L2andL3).
METHOD:Sincethebusinessusersarethemostindicatedtoprovideinputaround
businessneedsandhowthesystemadaptstothem,itmayhappenthattheusersdo
somevalidationnotcontainedinthescripts.TestteamwritetheUATtestcasesbased
ontheinputsfromEnduser(L1,L2andL3users)andBusinessAnalysts.
TIMING:Afterallotherlevelsoftesting(ExploratoryandFunctional)aredone.Only
afterthistestiscompletedtheproductcanbereleasedtoproduction.

TESTDELIVERABLES

S.No.
DeliverableName
Author
 Reviewer
1.
UATTestCases
TestTeam
BusinessAnalystsSignoff

TestEffortEstimate
ThisdocumentlistsoutalltheactivitiesthathavetobeperformedbytheQAteamandestimateshow
manymanhourseachactivityisgoingtotake.

Note:thisestimateisfortheTCOEteamonlyTestingSchedule
EXECUTIONSTRATEGY
EntryandExitCriteria
Theentrycriteriarefertothedesirableconditionsinordertostarttestexecution;
onlythemigrationofthecodeandfixesneedtobeassessedattheendofeachcycle.
Theexitcriteriaarethedesirableconditionsthatneedtobemetinorderproceed
withtheimplementation.
Entryandexitcriteriaareflexiblebenchmarks.Iftheyarenotmet,thetestteam
willassesstherisk,identifymitigationactionsandprovidearecommendation.Allthisisinputto
theprojectmanagerforafinalgonogodecision.
Entrycriteriatostarttheexecutionphaseofthetest:theactivitieslistedintheTest
Planningsectionofthescheduleare100%completed.
Entrycriteriatostarteachcycle:theactivitieslistedintheTestExecutionsection
ofthescheduleare100%completedateachcycle.
ExitCriteria
TestTeam
TechnicalTeam
Notes
100%TestScriptsexecuted

95%passrateofTestScripts

NoopenCriticalandHighseveritydefects

95%ofMediumseveritydefectshavebeenclosed

AllremainingdefectsareeithercancelledordocumentedasChangeRequestsforafuturerelease

Allexpectedandactualresultsarecapturedanddocumentedwiththetestscript
 AlltestmetricscollectedbasedonreportsfromHPALM

AlldefectsloggedinHPALM

TestClosureMemocompletedandsignedoff

Testenvironmentcleanupcompletedandanewbackupoftheenvironment

TestCycles
Therewillbetwocyclesforfunctionaltesting.Eachcyclewillexecuteall
thescripts.
Theobjectiveofthefirstcycleistoidentifyanyblocking,criticaldefects,
andmostofthehighdefects.Itisexpectedtousesomeworkaroundinordertogettoall
thescripts.
Theobjectiveofthesecondcycleistoidentifyremaininghighand
mediumdefects,removetheworkaroundfromthefirstcycle,correctgapsinthescripts
andobtainperformanceresults.
UATtestwillconsistofonecycle.
ValidationandDefectManagement
Itisexpectedthatthetestersexecuteallthescriptsineachofthecyclesdescribed
above.Howeveritisrecognizedthatthetesterscouldalsodoadditionaltestingiftheyidentifya
possiblegapinthescripts.Thisisespeciallyrelevantinthesecondcycle,whentheBusiness
analystsjointheTCOEintheexecutionofthetest,sincetheBUSINESSANALYSTshavea
deeperknowledgeofthebusinessprocesses.Ifagapisidentified,thescriptsandtraceability
matrixwillbeupdatedandthenadefectloggedagainstthescripts.
ThedefectswillbetrackedthroughHPALMonly.Thetechnicalteamwillgather
informationonadailybasisfromHPALM,andrequestadditionaldetailsfromtheDefect
Coordinator.Thetechnicalteamwillworkonfixes.
Itistheresponsibilityofthetestertoopenthedefects,linkthemtothe
correspondingscript,assignaninitialseverityandstatus,retestandclosethedefect;itisthe
responsibilityoftheDefectManagertoreviewtheseverityofthedefectsandfacilitatewiththe
technicalteamthefixanditsimplementation,communicatewithtesterswhenthetestcan
continueorshouldbehalt,requestthetestertoretest,andmodifystatusasthedefectprogresses
throughthecycle;itistheresponsibilityofthetechnicalteamtoreviewHPALMonadaily
basis,askfordetailsifnecessary,fixthedefect,communicatetotheDefectManagerthefixis
done,implementthesolutionpertheDefectManagerrequest.
DefectsfoundduringtheTestingwillbecategorizedaccordingtothebugreportingtoolMercuryHP
ALMandthecategoriesare:
Severity
Impact
1(Critical)
Thisbugiscriticalenoughtocrashthesystem,causefilecorruption,orcause
potentialdataloss
Itcausesanabnormalreturntotheoperatingsystem(crashorasystemfailure
messageappears).
Itcausestheapplicationtohangandrequiresrebootingthesystem.
2(High)
Itcausesalackofvitalprogramfunctionalitywithworkaround.
3(Medium)
ThisBugwilldegradethequalityoftheSystem.Howeverthereisanintelligent
workaroundforachievingthedesiredfunctionalityforexamplethroughanotherscreen.
Thisbugpreventsotherareasoftheproductfrombeingtested.Howeverother
areascanbeindependentlytested.