FREE Professional Java Developer, Automation Engineer, Business Analyst Training : HP ALM /Quality Center Tutorial for Beginners

Quality Center (QC) is a test management tools. HP Quality Center (QC), a commercial test management tool by HP
, supports various phases of software development life cycle. It is popularly known as HP-ALM Application Life Cycle Management.

It is now developed by HP as HP ALM Diagram Application life cycle management tool that supports various phases of the software development life cycle.

ALM (Application Life Cycle Management) is a web based tool that helps organizations to manage the application life cycle right from project planning, requirements gathering, until Testing & deployment, which otherwise is a time-consuming task.

ALM also provides integration to all other HP products such as UFT and load runner.

Why HP ALM ?

It enables all stakeholder to interact to achieve the project goal. It provides robust tracking and reporting various project. It provides detail project analysis and effective management.

Version:

HP ALM - supports all. best, complete access of all module

HP ALM essentials - supports basic features, access to requirement, test,defect management

HP QC - testing purpose, integration with unified functional test ( UFT)

HP ALM performance center edition - helps to run Load runner script. it helps to user to maintain , manage , execute and monitor the performance testing.

ALM work flows:

Release specifications ==> Requirement specifications ==> Test planning (test plan/test case) ==> Test Execution ==> Defect tracking ===> Analysis (graph and report created)

Components:

Enter a user name and password. select domain and project.

Domain: Domain is an independent business software department like ERP, CRM, banking etc.

Project: is independent software teams under a given department. . Eg.- in banking domain there could be project teams for net banking, treasury and wealth management etc.

Requirement modules:

Requirement module is used to store all requirements related to a testing project. Requirement are specified in Quality center by creating a requirements tree. Requirements tree is a graphical representation of requirement specification.Requirement can be grouped, sorted and monitored in the requirements pane.

Requirements can be linked to test created in test plan module ,defects in defect module. Later on, if a test requirement changes, you can immediately identify the affected test cases and defects.

Create a child and parent requirements.
view a requirements
Modify a requirements.

In QC

Create requirement from above text box. Then,

To add child requirement

create as much as child requirement

Requirements can be view in - 1. Tree view, 2. GRID view, 3, Numerations.

Tree view is good to know relationships among requirements.

Grid view is good for filtering and sorting of requirements.

Requirement can be modify, copy and edit.

Examples: basic functionality testing of Yahoo

Create Automated test to verify basic search functionality of Google. The step would be

Step 1. Launch browser and open the yahoo page.

step 2. Enter a search keyword say "book" and click search.

Step 3. Verify weather search result are generated.

Create New Test:

Step 1:

Step:

step 3:

Overview:

automate: from Quickest automation

automate script generate automatic

QTP Lunch:

QTP

automate script execute and lunch browser and save it.

check updated script

Test linkage:

test can be delete, copy paste run

Test and requirements can be linked :

linking can be done - 1. from a REQUIREMENT to a TEST 2. From a TEST to a REQUIREMENT

Add child: link yahoo login TEST with child-1 REQUIREMENT

select child requirement

click add icon

child

Link child-2 REQUIREMENT with Yahoo search TEST

click REQUIREMENT --> child 2

click covarage

select link to be added and click add

This is how test to be added to be requirement.

Modify and link tests

Test lab module:

Test lab module is used to run the test cases. The test run process begins with creating the test set tree and then running the tests. Initially test set folder is created. Depending on the testing goals you can add Tests to the test Set folder. Test sets can include both manual and automated test. You can include the same test in different test sets or add a few test instances to the same test set. You can set the date and time of execution of the test sets.

Test Lab:

create a test set
schedule a test
run a test

First create a folder

Then

select a folder and create a test set by clicking

after that new test set box appears.

enter test name

test case set can be created inside the sample folder

check open and close test set

Add TESTS from test plan module to the TEST SET

add test set yahoo and green arrow then

Now test set is ready.

Next step : EXECUTION FLOW:

schedule a test:

lets try

to test case run:

test run

execution flow:

A notification will sent to the assigned tester to start testing of Yahoo_Login on the scheduled day and time.

Yahoo_search can not be executed unless Yahoo_Login is finished.

Run TEST: - can be run two ways. 1. Manual, 2. Automatic

Run manual:

click begin run:

You will see step, expected result

click double square bottom and

lunch browser and run

run manually lunch browser

then update actual result

click next icon button

enter user name and password. then update Actual result

step 3:

Run automated test case:

Automated TEST run: QC will open the selected TESTING tool on your machine or a remote machine at designated day and time , execute the test run and update the Results in QC.

You can run certain specific or all tests in a TEST SET.

Lets click on automated test script

Click run. it runs automatically. You can run through IP address or run locally.

Click run button.

click on lunch

report generated

test is fail since search results were not generated in expected order

Defects Module:

Defects tracking is done in defects module. it is used to keep all data related to defects. defects can be added at any stage. defect can be added in test lab module while running a test case. it can be done by clicking on the new defect button in defect module.We can add defects by importing an excel.

Steps:

Create a Defect
Modify a defect
Email a defect
link a defect
add defect to favorite

create new defect:

New dialogue box appears and enter a short summery of defects.

Modify defect: double click defect

Defect Linkage:

You can link a test in your test plan to a specific defect in the defects grid. linkage is helpful when new test is created for a existing defect or there is a change in requirements which is linked to a defect. linkage can done directly and indirectly. when you directly link a defect to a run , QC indirectly links the defect to the Test instance , test Set , test and requirements.

Run step ==> Run ==> Test instance ==> test set and Test ==> requirement

However the linkage is unidirectional ie. when you link a defect to run, it is not indirectly linked to run step.

select yahoo test and

For link defect:

enter defect id:

You can also have an Option to create a new defect from TEST PLAN module and Link it to a TEST.

Favorites:

You can create favorite view in Quality center window with the settings you applied to it, Eg. in defects grid you may want to apply a filter to defects detected by you or assigned to you. A favorite view can be public or private.

create a Defects detected by you:

populated defected by Id:

Result

To add favorite: add to favorite

give a name:

set favorite as private or public

Traceability:

Why requirement traceability is required ?

Evolving requirements - if requirements change, it is important to identify when and why they changed so the QA team can change their Test plans accordingly.

Coverage - to ensure the QA team has covered all the requirements in their tests. This is essentially important when new requirements are added later in the project.

System maintenance - If a tester who has developed test cases without using traceability leaves the organization how would the replacing tester come to know from which requirements the test cases came from.

Tracing changes:

you can instruct QC create alerts automatically and send email to notify those responsible when changes occur in your project that may impact the testing process.

Traceability can be achieved in two ways: Automatic alert, Follow up alerts.

Automatic traceability alerts:

To generate automatic traceability alerts, you QC project administrator must activate traceability notification rules in project customization. Traceability notification rules are based on associations you make in QC between requirements, tested and defects. When an entity in your project changes, you are notified of any associated entities that may be impacted by the change.

Traceability alert could be generated when a requirement change, the designers of associated test are notified.

when a requirement change and it has associated tests, all project users are notified. When the status of a defect changes to "Fixed", the responsible tester of the test instance is notified. When a test runs successfully the users assigned to the associated defects are notified.

example

Follow up alerts:

you can use follow up flags to remind yourself to follow up on something.

You can set follow up flags for a test -

a test in the test plan tree or test grid
a test instance in the execution grid
a defect in the defects grid.

Graphs and Reports:

Analyzing testing process: Progress of the requirements, test plan, test runs and defect tracking can be evaluated by using Quality center reports and graphs. You can generate reports and graphs at any time during the testing process from QC.

Following are the three methods for this purpose

Generating reports
Generating graphs
Generating Live analysis graphs

Generating reports and graphs:

Quality center reports and graphs helps in analysis and quick decisions. Standard reports and graphs are available in each module like summary, progress or trend. Reports and graphs can be customized as per requirement.

Generating reports and graphs and add it to Favorite:

click on standard requirement report and click on configure report

click on filter item:

you can filter by Author id or any..

Reports are generated:

Add favorite: click favorite and name

you can see favorite button

Create a DEFECTS GRAPH and CUSTOMIZE IT:

In defect module choose analysis

result:

filter result

click on defect status closed:

click refresh to generate report

click on graph:

pie chart

Analysis of live graph:

You can crate live analysis to provide a dynamic and quick visual overview of all tests in the test subject folder or test sets in test set folder. live analysis differs from other graphs in that you do not have to recreate the graph to view data that has changed. Hence name "Live". Also layout and settings of graphs are preserved when you select another folder int he same module.

create graph: