Quality Assurance /
Software Testing Training
HP ALM QC
Page 2Classification: Restricted
Agenda
• HP ALM Overview
• HP ALM Solution
• HP ALM Segments
• QA Process
• Requirements
• Test Plan
• Test LAB
Page 3Classification: Restricted
HP ALM Overview
HP ALM empowers IT to manage the core application
lifecycle, from requirements through maintenance.
ALM simplifies and organizes application management by
providing you systematic control over the process.
It helps to create a framework and foundation for your
ALM workflow in a central repository.
Understands requirements, project milestones,
deliverables and resource and tracks the project health,
standards and quality
Aim of effective lifecycle management is greater
predictability, improved quality, and a ready
accommodation of change
Page 4Classification: Restricted
HP ALM Solution
Page 5Classification: Restricted
HP ALM Segments
Application lifecycle management is divided into two parts:
Site
Administration
• You can create and maintain
projects, users, servers, site
connections, license usage, and
parameters.
• You can also define site
administrators and change site
administrator passwords
Project
Management
• HP Application Lifecycle
Management provides project
planning and tracking so that
teams can define, track,
measure, and report on project
milestones and key
performance indicators
Page 6Classification: Restricted
QA Process
Application lifecycle management test process includes the following phases:
Specify Releases
Define Requirements
Develop Test Plans
Execute Tests
Log and Track Defects
Phase Description
Release
Specifications
Develop a release-cycle management plan to help
you manage application releases and cycles
efficiently.
Requirement
Specifications
Define requirements to meet your business and
testing needs.
Test Planning Based on the project requirements, you can develop
test plans and design tests.
Test Execution Create a subset of the tests in your project and
execute scheduled tests
Defect Tracking Submit defects and track their progress.
Page 7Classification: Restricted
Requirements
Page 8Classification: Restricted
Requirements Overview
• Requirements module is easy-to-use solution that helps the project
teams to assess the application functionalities meets business needs.
• Easily access requirements data through a centralized, web-based
repository accessible to the entire team
• Review requirements coverage and application quality to make better
application release decisions
• Prioritize requirements and align testing goals with business priorities
to enable compliance and manage change
• Validate application requirements and maintain traceability and an
audit trail among requirements, tests, and defects
Page 9Classification: Restricted
Creating Requirements
How to create a requirement?
Page 10Classification: Restricted
Step 1: Go to the Test Plan tab by choosing “Testing->Test Plan”.
Step 2: Select a Test
Step 3: Go to Req Coverage tab
Step 4: Click on “Select Req” to open the Requirement Tree
Step 5: Add requirement to the coverage grid to establish a link between the
test and the requirement
How to create Requirement Coverage
You can also add a requirement and its children to the grid
Page 11Classification: Restricted
Step 6: Right click on the requirement that has been added to the coverage grid of the test
Step 7: Select “Show Requirements details”
Step 8: Select “Test Coverage” from left pane
How to create Requirement Coverage
Shows the test
coverage
Page 12Classification: Restricted
How to create Test coverage
Step 5: Go to May Release folder and choose the option to create a new test.
Enter a name and select Manual
Page 13Classification: Restricted
Test Plan – Test Case Creation
Step 6: Enter other details. Designer name will be auto populated based on login
credentials. Click OK. The test gets added.
Page 14Classification: Restricted
Test Plan – Test Case – Test Step Creation
Step 7: Now you can add your steps. Click on the “Design Steps” tab. Click on
“New Step” icon.
Page 15Classification: Restricted
Test Plan – Test Case – Test Step Creation
Step 8: Enter the step details like Description and Expected Results fields come
up complete text editing features that are self explanatory.
Page 16Classification: Restricted
Test Plan – Test Case – Test Step Creation
Step 9: Create all the steps in the similar way
This completes the process of adding test cases and steps.
Page 17Classification: Restricted
Linking Test Case to Requirement
Step 1: Select the test case created. All the properties get displayed. Go to
“Req coverage” tab & click on “Select Req”
Page 18Classification: Restricted
Linking Test Case to Requirement
Step 2: The requirements tree gets displayed on the side. Expand the tree and
select the needed requirements
Page 19Classification: Restricted
Linking Test Case to Requirement
Step 3: Once done, close the requirement tree. You can link a test case to as
many requirements as you would like.
This completes the process of mapping
a test case to a requirement
Page 20Classification: Restricted
Linking Test Case to Requirement
Step 4: Let us now check, how this mapping effects the requirement. Go to
Requirements tab from the side bar. Double click on the requirement that you
just mapped and notice the “Test Coverage” details:
Since this test was just
created and never run, the
coverage status shows as
“No Run”
Page 21Classification: Restricted
Page 22Classification: Restricted
Test Plan Overview
 In Test Plan we can
 Organize subjects and tests in a test plan tree
 Create tests that define the steps for testing an application
 Use parameters in tests
 Generate test scripts from design steps
 Define test configurations
 Generate a live analysis graph from a test plan tree
Page 23Classification: Restricted
Test Case
Assume these are the test conditions for a release:
1) Login to Gmail with correct credentials
a. Enter correct user name, correct password and click login
b. Enter correct user name, correct password, select “Stay signed
in” and click login
2) Login to Gmail with incorrect credentials
a. Enter correct username, incorrect password and click Login
b. Enter incorrect username, correct password and click Login
c. Enter incorrect username, incorrect password and click Login
How do you write a manual test case for the same?
Page 24Classification: Restricted
Test Case
1(a) test case as an example
Lets take a look at how to create
the same test case in ALM
Page 25Classification: Restricted
Test Plan – Folder Creation
Step 1: Login to ALM into the right project. Create the release, cycles and
requirements.
Step 2: Go to the Test Plan tab by choosing “Testing->Test Plan”.
Step 3: Choose “Subject” as your home folder and create a sub folder “ALM
Training” under it.
Step 4: Create “May Release” and “June Release” Sub folders under it.
Page 26Classification: Restricted
Test Plan – Test Case Creation
Step 5: Go to May Release folder and choose the option to create a new test.
Enter a name and select Manual
Page 27Classification: Restricted
Test Plan – Test Case Creation
Step 6: Enter other details. Designer name will be auto populated based on login
credentials. Click OK. The test gets added.
Page 28Classification: Restricted
Test Plan – Test Case – Test Step Creation
Step 7: Now you can add your steps. Click on the “Design Steps” tab. Click on
“New Step” icon.
Page 29Classification: Restricted
Test Plan – Test Case – Test Step Creation
Step 8: Enter the step details like Description and Expected Results fields come
up complete text editing features that are self explanatory.
Page 30Classification: Restricted
Test Plan – Test Case – Test Step Creation
Step 9: Create all the steps in the similar way
This completes the process of adding test
cases and steps.
Page 31Classification: Restricted
Linking Test Case to Requirement
Step 1: Select the test case created. All the properties get displayed. Go to “Req
coverage” tab & click on “Select Req”
Page 32Classification: Restricted
Linking Test Case to Requirement
Step 2: The requirements tree gets displayed on the side. Expand the tree and
select the needed requirements
Page 33Classification: Restricted
Linking Test Case to Requirement
Step 3: Once done, close the requirement tree. You can link a test case to as
many requirements as you would like.
This completes the process of
mapping a test case to a requirement
Page 34Classification: Restricted
Linking Test Case to Requirement
Step 4: Let us now check, how this mapping effects the requirement. Go to
Requirements tab from the side bar. Double click on the requirement that
you just mapped and notice the “Test Coverage” details:
Since this test was just
created and never run, the
coverage status shows as
“No Run”
Page 35Classification: Restricted
Test LAB
Page 36Classification: Restricted
Test Lab Overview
 Test lab will help us create test sets that contains test cases that we need to
execute in each phase
 This is where the tester can execute the tests and record the test results
 Executed test results will be then mapped to the release cycle
Page 37Classification: Restricted
Test Case
Assume these are the test conditions for a release:
1) Login to Gmail with correct credentials
a. Enter correct user name, correct password and click login
Page 38Classification: Restricted
Test Lab – Test Set Creation
Step 1: Login to ALM into the right project.
Step 2: Go to the Test Lab tab by choosing “Testing->Test Lab”.
Step 3: Choose “Root” as your home folder and create a sub folder “ALM
Training” under it.
Step 4: Create a sub folder “May Release” under it.
Page 39Classification: Restricted
Test Lab – Test Set Creation
Step 5: Under May release, choose the option to create a new test set
Page 40Classification: Restricted
Test Lab – Test Set Creation
Step 6: Enter the test set name. Click OK
Page 41Classification: Restricted
Test Lab – Test Set Creation
Step 7: Once it is created. Click on “Select Tests” from the menu
Page 42Classification: Restricted
Test Lab – Test Set Creation
Step 8: Select the tests as required from Test Plan Tree
Page 43Classification: Restricted
Test Lab – Test Set Creation
Alternately if you choose the “Requirements Tree” tab, you can choose
requirement.
All the tests that are linked to it get added to your test set.
Page 44Classification: Restricted
Test Lab – Test Set Creation
Step 9: Go ahead and create all the test sets. As you can see from the screen
shot
This completes the process of creating
a test set and adding test cases to it
Page 45Classification: Restricted
Test Lab – Execution
Step 1: In the Test lab tab, choose the test set that you would like to run
Step 2: Click on “Run Test” or “Run Test Set”
“Run Test” will
execute the test case
selected
“Run test set” will
run the entire set one
test after the other
until the end
For an automation
test if the tool is
integrated, then it
launches and runs
it in the
automation testing
tool.
Page 46Classification: Restricted
Test Lab – Execution
Click on
Begin
Run
Page 47Classification: Restricted
Test Lab – Execution
Step 3: Since ours is a manual test, we will have to execute the steps manually
on our AUT and set the results.
Step 4: Go to the test status field and update. Enter the actual result in the
space provided.
Page 48Classification: Restricted
Test Lab – Execution
Page 49Classification: Restricted
Test Lab – Execution
Step 5: When done, click on the cross button to the dialog. The following
confirmation message is displayed. Click Yes
Page 50Classification: Restricted
Test Lab – Execution
This completes the process of
executing a test case from Test Lab
Page 51Classification: Restricted
Questions
Page 52Classification: Restricted
Thank You

HP ALM QC

  • 1.
    Quality Assurance / SoftwareTesting Training HP ALM QC
  • 2.
    Page 2Classification: Restricted Agenda •HP ALM Overview • HP ALM Solution • HP ALM Segments • QA Process • Requirements • Test Plan • Test LAB
  • 3.
    Page 3Classification: Restricted HPALM Overview HP ALM empowers IT to manage the core application lifecycle, from requirements through maintenance. ALM simplifies and organizes application management by providing you systematic control over the process. It helps to create a framework and foundation for your ALM workflow in a central repository. Understands requirements, project milestones, deliverables and resource and tracks the project health, standards and quality Aim of effective lifecycle management is greater predictability, improved quality, and a ready accommodation of change
  • 4.
  • 5.
    Page 5Classification: Restricted HPALM Segments Application lifecycle management is divided into two parts: Site Administration • You can create and maintain projects, users, servers, site connections, license usage, and parameters. • You can also define site administrators and change site administrator passwords Project Management • HP Application Lifecycle Management provides project planning and tracking so that teams can define, track, measure, and report on project milestones and key performance indicators
  • 6.
    Page 6Classification: Restricted QAProcess Application lifecycle management test process includes the following phases: Specify Releases Define Requirements Develop Test Plans Execute Tests Log and Track Defects Phase Description Release Specifications Develop a release-cycle management plan to help you manage application releases and cycles efficiently. Requirement Specifications Define requirements to meet your business and testing needs. Test Planning Based on the project requirements, you can develop test plans and design tests. Test Execution Create a subset of the tests in your project and execute scheduled tests Defect Tracking Submit defects and track their progress.
  • 7.
  • 8.
    Page 8Classification: Restricted RequirementsOverview • Requirements module is easy-to-use solution that helps the project teams to assess the application functionalities meets business needs. • Easily access requirements data through a centralized, web-based repository accessible to the entire team • Review requirements coverage and application quality to make better application release decisions • Prioritize requirements and align testing goals with business priorities to enable compliance and manage change • Validate application requirements and maintain traceability and an audit trail among requirements, tests, and defects
  • 9.
    Page 9Classification: Restricted CreatingRequirements How to create a requirement?
  • 10.
    Page 10Classification: Restricted Step1: Go to the Test Plan tab by choosing “Testing->Test Plan”. Step 2: Select a Test Step 3: Go to Req Coverage tab Step 4: Click on “Select Req” to open the Requirement Tree Step 5: Add requirement to the coverage grid to establish a link between the test and the requirement How to create Requirement Coverage You can also add a requirement and its children to the grid
  • 11.
    Page 11Classification: Restricted Step6: Right click on the requirement that has been added to the coverage grid of the test Step 7: Select “Show Requirements details” Step 8: Select “Test Coverage” from left pane How to create Requirement Coverage Shows the test coverage
  • 12.
    Page 12Classification: Restricted Howto create Test coverage Step 5: Go to May Release folder and choose the option to create a new test. Enter a name and select Manual
  • 13.
    Page 13Classification: Restricted TestPlan – Test Case Creation Step 6: Enter other details. Designer name will be auto populated based on login credentials. Click OK. The test gets added.
  • 14.
    Page 14Classification: Restricted TestPlan – Test Case – Test Step Creation Step 7: Now you can add your steps. Click on the “Design Steps” tab. Click on “New Step” icon.
  • 15.
    Page 15Classification: Restricted TestPlan – Test Case – Test Step Creation Step 8: Enter the step details like Description and Expected Results fields come up complete text editing features that are self explanatory.
  • 16.
    Page 16Classification: Restricted TestPlan – Test Case – Test Step Creation Step 9: Create all the steps in the similar way This completes the process of adding test cases and steps.
  • 17.
    Page 17Classification: Restricted LinkingTest Case to Requirement Step 1: Select the test case created. All the properties get displayed. Go to “Req coverage” tab & click on “Select Req”
  • 18.
    Page 18Classification: Restricted LinkingTest Case to Requirement Step 2: The requirements tree gets displayed on the side. Expand the tree and select the needed requirements
  • 19.
    Page 19Classification: Restricted LinkingTest Case to Requirement Step 3: Once done, close the requirement tree. You can link a test case to as many requirements as you would like. This completes the process of mapping a test case to a requirement
  • 20.
    Page 20Classification: Restricted LinkingTest Case to Requirement Step 4: Let us now check, how this mapping effects the requirement. Go to Requirements tab from the side bar. Double click on the requirement that you just mapped and notice the “Test Coverage” details: Since this test was just created and never run, the coverage status shows as “No Run”
  • 21.
  • 22.
    Page 22Classification: Restricted TestPlan Overview  In Test Plan we can  Organize subjects and tests in a test plan tree  Create tests that define the steps for testing an application  Use parameters in tests  Generate test scripts from design steps  Define test configurations  Generate a live analysis graph from a test plan tree
  • 23.
    Page 23Classification: Restricted TestCase Assume these are the test conditions for a release: 1) Login to Gmail with correct credentials a. Enter correct user name, correct password and click login b. Enter correct user name, correct password, select “Stay signed in” and click login 2) Login to Gmail with incorrect credentials a. Enter correct username, incorrect password and click Login b. Enter incorrect username, correct password and click Login c. Enter incorrect username, incorrect password and click Login How do you write a manual test case for the same?
  • 24.
    Page 24Classification: Restricted TestCase 1(a) test case as an example Lets take a look at how to create the same test case in ALM
  • 25.
    Page 25Classification: Restricted TestPlan – Folder Creation Step 1: Login to ALM into the right project. Create the release, cycles and requirements. Step 2: Go to the Test Plan tab by choosing “Testing->Test Plan”. Step 3: Choose “Subject” as your home folder and create a sub folder “ALM Training” under it. Step 4: Create “May Release” and “June Release” Sub folders under it.
  • 26.
    Page 26Classification: Restricted TestPlan – Test Case Creation Step 5: Go to May Release folder and choose the option to create a new test. Enter a name and select Manual
  • 27.
    Page 27Classification: Restricted TestPlan – Test Case Creation Step 6: Enter other details. Designer name will be auto populated based on login credentials. Click OK. The test gets added.
  • 28.
    Page 28Classification: Restricted TestPlan – Test Case – Test Step Creation Step 7: Now you can add your steps. Click on the “Design Steps” tab. Click on “New Step” icon.
  • 29.
    Page 29Classification: Restricted TestPlan – Test Case – Test Step Creation Step 8: Enter the step details like Description and Expected Results fields come up complete text editing features that are self explanatory.
  • 30.
    Page 30Classification: Restricted TestPlan – Test Case – Test Step Creation Step 9: Create all the steps in the similar way This completes the process of adding test cases and steps.
  • 31.
    Page 31Classification: Restricted LinkingTest Case to Requirement Step 1: Select the test case created. All the properties get displayed. Go to “Req coverage” tab & click on “Select Req”
  • 32.
    Page 32Classification: Restricted LinkingTest Case to Requirement Step 2: The requirements tree gets displayed on the side. Expand the tree and select the needed requirements
  • 33.
    Page 33Classification: Restricted LinkingTest Case to Requirement Step 3: Once done, close the requirement tree. You can link a test case to as many requirements as you would like. This completes the process of mapping a test case to a requirement
  • 34.
    Page 34Classification: Restricted LinkingTest Case to Requirement Step 4: Let us now check, how this mapping effects the requirement. Go to Requirements tab from the side bar. Double click on the requirement that you just mapped and notice the “Test Coverage” details: Since this test was just created and never run, the coverage status shows as “No Run”
  • 35.
  • 36.
    Page 36Classification: Restricted TestLab Overview  Test lab will help us create test sets that contains test cases that we need to execute in each phase  This is where the tester can execute the tests and record the test results  Executed test results will be then mapped to the release cycle
  • 37.
    Page 37Classification: Restricted TestCase Assume these are the test conditions for a release: 1) Login to Gmail with correct credentials a. Enter correct user name, correct password and click login
  • 38.
    Page 38Classification: Restricted TestLab – Test Set Creation Step 1: Login to ALM into the right project. Step 2: Go to the Test Lab tab by choosing “Testing->Test Lab”. Step 3: Choose “Root” as your home folder and create a sub folder “ALM Training” under it. Step 4: Create a sub folder “May Release” under it.
  • 39.
    Page 39Classification: Restricted TestLab – Test Set Creation Step 5: Under May release, choose the option to create a new test set
  • 40.
    Page 40Classification: Restricted TestLab – Test Set Creation Step 6: Enter the test set name. Click OK
  • 41.
    Page 41Classification: Restricted TestLab – Test Set Creation Step 7: Once it is created. Click on “Select Tests” from the menu
  • 42.
    Page 42Classification: Restricted TestLab – Test Set Creation Step 8: Select the tests as required from Test Plan Tree
  • 43.
    Page 43Classification: Restricted TestLab – Test Set Creation Alternately if you choose the “Requirements Tree” tab, you can choose requirement. All the tests that are linked to it get added to your test set.
  • 44.
    Page 44Classification: Restricted TestLab – Test Set Creation Step 9: Go ahead and create all the test sets. As you can see from the screen shot This completes the process of creating a test set and adding test cases to it
  • 45.
    Page 45Classification: Restricted TestLab – Execution Step 1: In the Test lab tab, choose the test set that you would like to run Step 2: Click on “Run Test” or “Run Test Set” “Run Test” will execute the test case selected “Run test set” will run the entire set one test after the other until the end For an automation test if the tool is integrated, then it launches and runs it in the automation testing tool.
  • 46.
    Page 46Classification: Restricted TestLab – Execution Click on Begin Run
  • 47.
    Page 47Classification: Restricted TestLab – Execution Step 3: Since ours is a manual test, we will have to execute the steps manually on our AUT and set the results. Step 4: Go to the test status field and update. Enter the actual result in the space provided.
  • 48.
  • 49.
    Page 49Classification: Restricted TestLab – Execution Step 5: When done, click on the cross button to the dialog. The following confirmation message is displayed. Click Yes
  • 50.
    Page 50Classification: Restricted TestLab – Execution This completes the process of executing a test case from Test Lab
  • 51.
  • 52.