HP ALM Online Training by Cheyat Tech

8/18/2019 HP ALM Online Training by Cheyat Tech

1/21

http://cheyat.com/qa/hp-alm-onli

ne-training-tutorials

HP ALM Online Training

http://cheyat.com/qa/hp-alm-online-training-tutorialshttp://cheyat.com/qa/hp-alm-online-training-tutorialshttp://cheyat.com/qa/hp-alm-online-training-tutorialshttp://cheyat.com/qa/hp-alm-online-training-tutorials


2/21


3/21

Why Testing

3


4/21


5/21

Test management is the practice of organi!ing and

controlling the process and artifacts required for thtesting e"ort#

• Pen and paper

• $ord processors• %preadsheets• %haring in &rives '()*+• ,mails

-raditional toolsused for testmanagement

include)

Why Test Management Tools


6/21

.

• %tart test management activities early• -est iteratively• Reuse test artifacts• /tili!e requirements0based testing•

1everage remote testing resources• ,nd to ,nd -raceability of Release requirements• &ening and enforcing a eible testing process• 5oordinate and integrate with the rest of development• 5ommunicate status• 6ocus on goals and results• 7utomate to save time

Test Management Recommendations


7/21

Benets

8


8/21

9

ALM !takeholders

Pro:ect;anagers


9/21

Domain "ro#ects

76?@Pro:ects @ 7ll

76?@ R65@7ll

76?@


10/21

Testing "rocess – An *+er+iew ,!*LMA- – '"ALM.

%C1;7E HP 71; F2

Requirements

&efects toprocess in%C1;7E


11/21

Testing "rocess – Details ,!*LMA- – '" ALM.

Requirements ;odule

F# -he Requirements can be loaded to HP 71; in any of the following three ways• Import are ,port the business blueprint and test ob:ects from %C1;7E %C17R2J

$ote% &nly t'e Business (rocesses)scenarios t'at 'as test object or transactions assigneimport to *( +L!

• 5apture the functional requirements in the dened ecel spreadsheet and import the sam• 5reate the required folder tree and enter requirements into that based on the functional r2# Cnce the Requirements are imported to the HP 71; then we can update*delete the requiremen

respective requirement


12/21

Test "lan ModuleF# -he test cases can be loaded to HP 71; in any of the following two ways

• &irectly enter the test cases and dene the test steps in the -est plan module• $rite the test cases in the dened ecel spreadsheet and import the same to HP 71; tes

2# ,ach test case will be mapped to the corresponding requirements by editing the test case

Test La$ Module3# -he corresponding test cases need to be mapped pull to the -est lab module as a -est set for th4# -hese test case need to be eecuted either ;anually or 7utomated run for the automated case# -he test results must be transferred to !*LMA- K !*LAR/0)!*LAR/1

Testing "rocess – Details ,!*LMA- – '" ALM.contd2


13/21

De&ects ModuleF# &uring the test eecution the defects can be logged when the testing scenario is fail to meet t2# &efects falling under two types)

02 De&ect) It is a regular defect that is been identied as to be processed in the HP 71; onl&evelopment team and it goes though the defect lifecycle process in 71;

12 !A" related De&ect3 It is a defect that is been identied as to be processed in the %C1;team and it goes through the defect lifecycle process in %C1;7E '&efect 6i+ and 71; '&and 5losing +

• -hese can be viewed in the %RM4D-*4M*-5T*R or !M4W*R6%(-T(R or %RMcodes in %C1;7E

Testing "rocess – Details ,!*LMA- – '" ALM.contd2

HP 71; %C1

Eew

Eew

6ied

5losed

6or

ReceH

Propos

5on

7ssignresponsibility to %7P


14/21

De&ect Work7ow

HP ALM Implementation Case Study


15/21

HP ALM Implementation Case Study

5lient is one of the largest company that

o"ers a comprehensive array of nancial

services to retail and institutional clientsL

which includes annuitiesL retirement plansL

life insuranceL mutual fundsL managed

accountsL alternative investmentsL direct

bankingL institutional investment

managementL employee benetsL and

nancial planning#

5lient Prole

5lient Requirements

-he client was looking to implement HP 71;

to address the following)

;anage and create traceability between

requirementsL tests artifacts and defects

%tandardi!e process across application

lifecycle 6acilitate collaboration and

communication between multipleL

distributed teams

;anage and eecute automated testing

;ake informed go*no go decisions

Provide a scalable architecture

Pro:ect


16/21

ciency by reducing duplication of e"ort and sharing best

practices

Increased visibility to quality statusL requirement coverage and defect

trends in aggregate across pro:ects and initiatives

7chieved signicant savings by tracking key metrics against pro:ect

milestones within Pro:ect Planning and -racking of HP 7pplication

;anagement


17/21

%ategory Description

De&ect$hen a defect is logged itJs categori!ed as O&efect by default# It states that the de

analy!ed and ed for the current release

5ssue$hen a defect is identied and after reviewing Lit has few dependencies to be veri

steps to be carried etc# hence the defect will be categori!ed as Issue

-ew Req

$hen a defect is logged in which the test carried to related to that defect is not men

-hen the defect is considered as a OEew Req and it goes through the 5hange requ

following today#

De&ect %ategories

De&ect !tatuses 9 Descriptions


18/21

!tatus Responsi$ility Target *wner Description

-ew -ester -est 1ead• -ester*


19/21

"riorityLe+el

Business 5mpact Testing 5mpact

"0

-his has severe impact to the customer and continuing to

operate may not be possible# -his must be ed

immediately#

&efect is a blocking issue# -he defect would impact th

iteration if not resolvedL and any testing cannot proce

"1

-his is ma:or impact to the customer but does not halt

operations# -his must be ed as soon as possible and

before the release of the current version in development#

&efect is severe# -his impacts the general behavior of

may eist but its use is unsatisfactory# -est cases will b

":

-his has ma:or impact to the customer# -he problem should

be addressed and ed with the current version release if

time permitsL or a patch to the release issuedL if possible#

-he failure impacts non0critical aspects of the system

under specic conditions# &uring testing this will resul

not block the eecution of the other test cases#

";

-his has minor impact to the customer# -he aw is usually

cosmetic to the customer in nature and only needs to be

ed when there is su>cient time#

5osmetic problem# &uring testing this will result in tes

block the eecution of the other test cases#

De&ect "riority le+els

Priority is an outcome of sub:ective evaluation of how important an issue to the business# Cther tasks in the quare factors that may impact the decision of prioriti!ing the &efect# It is relativeL it shiftsL and it is always a bus

• Initial value for priority eld will be set by the tester who creates the defects based on testing impact# &urimeeting it business re0evaluates and updates the valueL if needed#

• &,=*business will participate in the defect triage meeting during the -esting '6unctional*%I-*Regression+ doassign * change the priority to new defects based on business impact#


20/21

Reports and

Re:ected

&eferred

5losed

Retest

6ied

7ssigned

Eew

/- %I- /7-

2

4

.

9

F

F2F4

F.

F9

2

24

2

2

4

42

4.

2

4 4

2

4 4

Test !ummary Report =as o


21/21

1ab

Documents

HP ALM Online Training by Cheyat Tech