HP ALM Introduction

HP ALM (Application Life Cycle Management)

It is a Test Management Tool from HP.

ALM Supports:

•    Requirements Management
•    Test Design
•    Test execution
•    Defect management
•    Traceability
•    Integration with other Tools like UFT and LoadRunner.

ALM Tool Version History:

i) TestDirector (1.0 to 8.0) Versions

MS Access
SQL Server
ii) Quality Center (8.0 to 11.00)

MS SQL Server
iii) ALM 11.5

ALM 12.01 (Latest Version)
UFT and ALM Integration
a) Stand-alone Environment
UFT Installation

ALM Installation

UFT Add in for ALM
b) Intranet Environment

Server side:

ALM Installation
Client side:

UFT Installation

ALM Client version Installation

UFT Add in for ALM
ALM Supports:

Stand alone environment

Intranet environment

Internet environment

for sharing resources as well as services.
In case of UFT
UFT can share Resources only.

UFT Tool Resources                   
Shared object Repository file
Function Library file
Environment Variables file
UFT Tool Services
Data Table
Step generator etc...
ALM doesn't have any programming interface

ALM has Database engine to support SQL Commands

It has Command Line interface, we can execute SQL Commands

ALM supports all types software Applications by default.

ALM is only for Documentation and generating Reports, it doesn't interact with software Applications

ALM Add ins
a) MS Word

b) MS Excel

To import data from File system to ALM Project

Three things can be imported:

a) Requirements

b) Tests

c) Defects
Usage of ALM
i) Functional Testing (Manual) + Test Management (ALM)

ii) Some Functional Testing (Manual) + Some Functional Testing (UFT) + Test Management (ALM)

iii) Some Functional Testing (Manual) + Some Functional Testing (UFT) + Performance Testing (LoadRunner) + Test Management (ALM)

iv) Functional Testing (Manual) + Performance Testing (LoadRunner) + Test Management (ALM)

UFT Tool can be accessed by Testers and Customers

ALM can be accessed by Development Team, Testing Team, BA and Customers etc...
Users of ALM (Testing Team)

i) Site Admin for handling all ALM projects

ii) Project Admin (Test Lead) to handle one or more projects

iii) General User (Tester) to work with one or more projects
ALM has 2 interfaces

I) Site Admin / Server side

II) ALM / Client side interface
Import features in Site Admin:

a) Create / delete Domains

b) Create / Edit / Delete Projects

c) Create / Edit / Delete Users

d) Assign users to projects

e) Track project status
ALM Interface
a) Requirements
    Create/Edit/Delete Requirements and Child requirements
    Import Requirements from file System using either MS Word or Excel format.

b) Test Plan (It is an area where we create Manual and Automated Tests)
    Create/Edit/Delete Manual Tests
    Create/Edit/Delete Automation Tests(* Using Automation Tool)
    Import Tests from file System using either MS Word or Excel format.
    Map Tests with Requirements

c) Test Lab (It is an area where we execute Manual and Automated Tests)
    Create Test Batches
    Execute Manual Test batches or Tests
    Execute Automated Tests
d) Defects
    Post Defects
    Track Defects
    Import defects directly from UFT Result window
    Import Defects from file System using either MS Word or Excel format.


Post a Comment