Click here to load reader

HP ALM Defect Management Training

  • View
    27

  • Download
    2

Embed Size (px)

DESCRIPTION

HP training

Text of HP ALM Defect Management Training

Slide 1

HP Application Lifecycle Management Defect Management TrainingKelly HayduTesting Center of Excellence ManagerJune 2013

AgendaReview the Defect Workflow Where we wereHow we got to where are todayWhere we are todayTraining on HP ALM Defect Management module

2

Where we were

3MS Project Issue Management used to defect tracking for the Way to Work implementations

Why we are making a change

4Need for visibility into the product quality and stabilityDefects are expensive $$$$$Creating one central location for entering defects and standardizing the process helps eliminate: Mass amounts of email and the telephone game Lack of auditing and no system of recordWorking in silos (duplicate defects)Creates cross-pollination between groups reducing multiple people working on the same issue

How did we get to where we are now

5MS Project Issue Management vs HP ALM Defect ManagementAnalysis of MS Project Issues Management used for the LAM implementationAnalysis of standard HP ALM Defect Management fields, values and workflowComparison of fields and values between two systemsWhat can we use out of the box vs customizations needed in HP ALM Defect Management module

How we got to where we are now

6Define a common Defect Workflow

How we got to where we are now

7Customizations to HP ALM Defect ManagementVBScripting used to:Accommodate our workflow Define user group permissionsSetup email notifications and alertsIT Directors and Managers reviewed the workflow and had demo of new systemAdditional enhancements and recommendations were made after review Approval of system was given prior to training and roll-out

Where we are today

8Fully defined Defect WorkflowDocumented Defect Process, Quick Tip GuideCustomized HP ALM Defect Management moduleGeneric enough for use throughout all projects

Where we are today

9Roll-out StrategyPhase 1K2 Wave 1: Realization, IT1, and IT2 teamsPhase 2K2 Wave 1: HAPM Business LeadsPhase 3K2 Wave 1: Business Users for UAT (subject to change)Phase 4 AMS (Managed Services)

What will not change

10Enhancement requests, and production issues will continue to be maintained in ServiceNow

What is considered a defect?

11

Data problemsConfiguration changesCode issuesDocumentation and/or Requirement changes, clarifications or issues

Users of Defect Management

12SubmitterProject ManagerFunctional LeadDeveloperQA TesterQA Manager

Definition of Submitters role for Defect Management

13SubmitterAnyone who finds an issue with the systemResponsible for testing issues that are deemed as Not Reproducible closing the issue when it is not reproducibleProvides clarifications, data, steps to reproduction, screenshots, etc.

Definition of Project Managers role for Defect Management

14Project ManagerResponsible for triaging and assigning defects

Definition of Functional Leads role for Defect Management

15Functional LeadAnalyses and owns the defectDetermines if it is a duplicate, not reproducible, not a defect, or is a valid issueWorks with the submitter on clarifications or issues that are not reproducibleMakes the appropriate changes and fixes the defect to their best abilityAssigns defect to a Developer when changes in code are requiredProvides all necessary information to the Developer and QA Tester in order to for the defect to be successfully completed.

Definition of Developers role for Defect Management

16Developer Works with the Functional Lead to ensure that the defect is reproducibleMakes the appropriate code changes to a defectServes as a second check to determine if the defect is a duplicate

Definition of QA Testers role for Defect Management

17QA TesterResponsible for testing the defect and ensuring that quality remains to be sustained in the product(s)Gatekeeper for closing an issue, unless it is tested by the original submitter.

Definition of QA Managers role for Defect Management

18QA ManagerResponsible for triaging defectsGenerating defect trends and reportingUnderstanding the health of a product

Decide what type of issue you have

19

Type is categorized as follows:Data IssueProblem with a piece of data DefectError, flaw, failure or fault in the system that produces an incorrect or unexpected result, or causes it to behave in unintended waysRequirements ClarificationNeed for more information or questions about documentation, such as a Blueprint, Business Process, etc.Security IssueAuthorization or authentication problems, such as SAP Securityhttp://en.wikipedia.org/wiki/Software_bug

Defect Workflow

20

New Defect WorkflowSubmitter adds a new defectDefect automatically assigned to the Project Manager future enhancementDefect status automatically changes to Open upon submissionProject Manager receives an email when defect is assigned to he/she

Project Managers role

21Project Manager will determine the following:Defect should be closedDefect should be postponedDefect should be worked on and remain open

Project Managers role22Determines defect should be closed

Required fields:Comments add why it is being closedTested byTested in EnvironmentClosed Date automatically set to current date

Project Managers role23Determines defect should be postponedRequired fields:Comments add why it is being postponedTargeted Release Targeted CycleClosing Date field is hidden

Project Managers role24Determines defect should remain open and assigned for investigationAssigns to Functional Lead

Functional Leads role25Analysis of the defect. Determines if defect is:Not ReproducibleDuplicateNot a DefectRequires a fixConfiguration changeCode change

Functional Leads role26Determines defect is Not ReproducibleWorks with Submitter to identify if problem is valid

Functional Leads role27Determines defect is a DuplicateAdds notes referencing duplicate defect #

Functional Leads role28Determines defect is Not a DefectAssigns defect to QA Tester Adds notes indicating how the system should work and the Business Process, when applicable

Functional Leads role29Determines there is a configuration change needed and makes the fixAssigns defect to QA Tester Adds notes indicating what was fixed and areas for regression testing

Functional Leads role30Determines there is a code change requires or further analysis needs to be performed by DeveloperAssigns defect to DeveloperAdds notes indicating what was tested and any supporting documentation

Developers role31Investigates the defect and code to determine if a code change is requiredDetermines the defect:Not ReproducibleDuplicateNeeds to be fixed

Developers role32Determines defect is Not ReproducibleAssigns defect back to Functional Lead

Developers role33Determines defect is a DuplicateAdds notes referencing duplicate defect #

Developers role34Determines a code change is requiredMakes appropriate change and sets the defect to FixedAdds notes indicating what was fixed Assigns to QA for testing

QA Testers role35Tests changes made to resolve a defectDetermines if test results in Pass or FailPass = ClosedFailed = Rejected

Defect is Fixed and can be Closed

Defect is tested and passesTester changes defect Status to Closed

Required fields:Comments add what was tested and what failedTested in EnvironmentTested By automatically set to Assigned toClosing Date is automatically set to current date

36

36

Defect is tested and Not Fixed

Defect is tested and failsTester changes defect Status to RejectedAssigns to Developer or Functional Lead depending on who made the fixAdds testing notes

37

37

Reopening a defect...

Rule of thumb for reopening a defectProblem must be exactly the same, no variance

38

38

Defect is found again and set to Reopen

Defect is set to ReopenTester or Submitter changes defect Status is to ReopenClosing Date automatically set to emptyAssigned to automatically set to emptyAssignment should be made to Project Manager for triage39

39

Defect is found again and set to Reopen

Defect is set to ReopenTester or Submitter changes defect Status is to ReopenClosing Date automatically set to emptyAssigned to automatically set to emptyAssignment should be made to Project Manager for triage40

40

Demo

Lets go for a test drive.Vrrrrooooommmm41

41

How to get into the Defect Management module

HP ALM is a web based application It can be accessed using the following URL:http://usnpkhpqcdb01:8080/qcbin/start_a.jspEveryone will be required to have a name and password to sign into the applicationUser names and passwords will be sent individually Passwords can be changed per user: In HP ALM > Menu Item Tools > Customize > User PropertiesPrivileges were granted based on the users role42

42

Tips for the Defect Management moduleYou can set your own personal defect defaultsBest to set if you are entering defects frequently in the same application, functional area, process, etc. * means a required fieldAdd the value or you will get annoyed by the messages!Dont ignore your email! When you are assigned a defect, the system will send you an email. Read the email or make a conscious effort to frequently check your defect queue.Add detailed steps to reproduce the issueDo not assume everyone knows how you found an issue!Include as much detail as possible or the defect will come back to haunt you (more information required please)

43

43

Follow-up and going LiveGo-Live is July 1stUnderstand there will be bumps in the road. Please b

Search related