HP ALM Test Lab Module To protect the confidential and proprietary information included in this material, it may not be disclosed or provided to any third parties without the approval of QA TRAINING EXPERTS.

AGENDA Add Defect Link – will be covered later Modify Defect Link – will be covered later Remove Defect Link – will be covered later

Introduction

Navigating to the Test Lab Introduction Navigating to the Test Lab The Test Lab module is where tests are executed from and results are tracked.

Introduction Test Lab module is used to create test sets and perform test runs, this can be viewed by clicking the Test Lab button on the sidebar of window.

Introduction Test Lab is split into 2 sides Tree View Execution Grid View

Introduction The Tree View is where you can create test folders and test sets. Folders are used to organized test sets A Test Set is a container for tests to be executed.

Introduction The Execution Grid is where tests are executed from. It is also where test execution can be tracked.

The Test Lab Window

The Test Lab Window A Test Sets contain tests The execution grid is where tests are found and executed

Adjusting Your Columns The Test Lab Window Adjusting Your Columns To simplify your view, remove unneeded columns You must have a Test Set selected to see the column button

Steps to Execute a Test

Steps to Execute a Test Steps to Execute a Test from ALM ALM is used to track the execution of tests. To accomplish this a tester must execute each step of test, determine if the step worked as expected and then mark the step as Passed or Failed. If every step of a test passes then the entire test will show Passed. If a step fails then you will be required to document a defect to represent the problem. Find your folder Select the Test Set Select the Test Start the Run Begin Run Resize Manual Runner Pass or Fail Each Step Capture the Actual Result Stop the Run Steps to Execute a Test from ALM

Steps to Execute a Test From the Test Set Tree, find your folder and expand it by clicking on the arrow.

Steps to Execute a Test Begin Run starts the test

Steps to Execute a Test The manual running window must be resized to see each part of the window.

Steps to Execute a Test Images can be opened for better viewing

Steps to Execute a Test The key parts of the manual runner window

Execution toolbar Steps to Execute a Test “Always on Top” feature – Keeps the runner window open at all times. Helpful so you don’t have to keep toggling back and forth between screens Ellen Alternate SC Slots: 11:30 – 12:30 Thursday Create Defect Pass / Fail Step Add Attachment / Screenshot Stop Test Run

Steps to Execute a Test Each step of a test must be marked as Passed or Failed

Steps to Execute a Test Different Statuses of a Test Run

Steps to Execute a Test Failing a step is very similar to passing a step. You click the Fail button instead of Pass.

Steps to Execute a Test When your finished executing all of the steps or maybe you ran out of time, use the stop button to stop the Test Run

Stopping a Test Before it is Finished

Stopping a Test before it is finished More on Executing Tests Stopping a Test before it is finished If you don’t have enough time to finish a test you can stop it and continued it from where you left off

How to Continue a Test

More on Executing Tests How to Continue a Test The Continue Manual Run option must be used to continue a previous run.

How to Re-Run a Test

More on Executing Tests How to Run a Test Again If you need to re-run a test, just follow the same steps as before. It will start a new test run.

How to Report a Defect

How to Report a Defect Defects are reported as a result of a failed step in a test. Important: Before reporting a defect, it is recommended that you first fail the step and add a comment to “Actual”

Reporting a defect is just a click of a button How to Report a Defect Reporting a defect is just a click of a button

How to Report a Defect How to fill out the New Defect report Important! Make sure you search the defects before reporting a new one to check if the problem has already been reported.

How to Report a Defect After submitting the defect, you will return to the manual runner to allow you to continue testing the remaining steps or click stop to end the test run.

How to Report a Defect You can attach a file, url, snapshot, system info, or the clipboard to a Defect.

Attachments & Taking a Snapshot Click Attachments Click to attach a file such as a .pdf or MS Excel export. Ellen Alternate SC Slots: 11:30 – 12:30 Thursday Click to take a screenshot. Will open new window: If you click once on the screen you wish to capture, it will capture the entire screen. Otherwise, click to specify the region of the screen to capture.

Linking of Defects Responsible vs. tester Test instance window Run details Run Step details

Defect Linking

Attachments and Defect Linking A defect can be linked to each different entity type in HP ALM Requirements Tests Test Set Test Instance Runs Run Steps And Other Defects

Attachments and Defect Linking From the Test Lab defects can be linked to: Test Sets Test Instances Runs Run Steps

Attachments and Defect Linking To understand these entity types lets break down an executed test into the various layers Test Set – Is a group of tests to be executed. Test Instance – Instance means occurrence. When a test is added to a test set in the test lab module it is referred to as a test instance. Each test in a test set is a Test Instance. Run – Represents a test that was executed. Every time a test is run (executed) it is automatically given a unique Run Name and Run ID. Run Step– Is the same as a test step. A Run Step is a unique entity given to a test step when it is executed in a test instance. A Run Step is associated with a specific Run.

Attachments and Defect Linking Linking a Defect to each entity type Test Set – We link a defect to the test set if it impacts several test instances within the test set. Test Instance – We link a defect to the test instance if it impacts more than one step of the test instance. Run – We link a defect to a Run if it doesn’t go with a specific step but impacts the functionality being tested with the test. Linking a defect to a run shows the outcome of that specific run. Run Step – We link a defect to a Run Step if it impacts a specific step of a Run.

Attachments and Defect Linking We link defects to tests to understand the reasons for it being marked as blocked or failed. When a defect has been resolved we can refer to the link to know which tests can not be retested.

Test Set Click on the Linked Defects tab Choose which test set you want to view Change this to “All Links” to view all defects linked to any entities; test sets, tests, runs, and/or steps Direct Link only shows defects linked to the test set. Use these buttons to link either a new defect or an existing

Test Instance Click on the Details button Select the test you want to look at Change this to “All Links” to view all defects linked to any entities; tests, runs, and/or steps Direct Link only shows defects linked to the test instance. Use these buttons to link either a new defect or an existing Click on Linked Defects

Run Click on the Details button Select the test Click on Runs to view the runs Select the run Click on the Details button to open the Run Details window Click on Linked Defects Change this to “All Links” to view all defects linked to any entities; runs, and/or steps Direct Link only shows defects linked to the particular run.

Attachments and Defect Linking Run Step Select Steps Select which Step you want to look at Change this to “All Links” to view all defects linked to all steps; Direct Link only shows defects linked to a particular run step. Click on the Details button Attachments and Defect Linking Click on Linked Defects

ALERTS

Alerts Alerts