Hp-QC Tutorial: Quality Center - Test Lab

Test Lab

This module helps the testers to execute the created tests. One can schedule, run and analyze, post defects using this module.

The Following functionalities in Test Lab module helps us to understand test lab module in depth.

Functionality	Description
Creating Test Set	This functionality describes how to create and define test sets in the Test Lab module.
Test Run Schedules	Helps the testers to control the execution of test instances in a test set.
Test Execution	Enables testers to execute the test/test set.
Test Results	This Functionality enables testers to analyze the test results.

Test Set

Once test design using Test Plan module is completed, testers organize test execution by creating test sets in the Test Lab module. A test set contains a set of the tests that are designed to achieve specific test goals.

HL ALM supports different types of test sets and are listed below:

• Performance
• Functional
• Default

Below are the steps to create test sets in Test Lab module.

Step 1 : Create a Root folder as a container for having the test sets. Name it inline with the release and cycle so that it is easy to track.

Step 2 : Upon creating root folder, testers can assign it to a specific cycle on root folder level. Only if it is mapped to a particular cycle, we can track the test results based on a cycle.

Step 3 : Create a new test set by entering the type, description and attach documents/attachments if any.

Step 4 : Upon creating a test set, the details can be accessed using details tab.

Step 5 : Select "Execution Grid", the "Select Test" Button would be activated as shown below.

Step 6 : When "Select test" button is clicked, Test Plan tree opens for the user to select the tests into this test set.

Step 7 : In "Execution Flow" tab shows how the tests are organized.

Step 8 : "History" Tab shows the sequence of changes that this particular test set underwent since the user created.

Test Run Schedules

The test execution can be controlled using "Execution Flow" Tab. Testers can specify a date and time, and set conditions for executing a particular test instance. It is usually based on results of another specified test instance in the Execution Flow.

Now, let us see the step by step procedure on how to schedule the test flow in HP-ALM.

Step 1 : Select "Execution Flow" tab from Test Lab module.

Step 2 : Right click on the test instance and select "Test Run Schedule" as shown below.

Step 3 : Run Schedule window opens as shown below. Click on "+" icon.

Step 4 : New Execution Condition window opens. In this window we can select the test which would be precondition for the selected test. We can make it as a prerequisite to pass or finish the test before the selected test is executed.

Step 5 : Run Schedule window displays the option that is selected by the user.

Step 6 : The Execution flow realigns automatically as show below.

Step 7 : The same process can be repeated for Time Dependancy setting which will be triggered only after that specified time.

Step 8 : Scheduler realigns based on the specified date and time as shown below.

Test Execution

After creating a test set, scheduling, test execution comes into the picture. Upon Execution we compare the actual result against expected result and raise defects if any. Following are the steps for test execution.

Step 1 : Select the tests that you would like to execute and click Run Button. Three options would be shown to the user.

Step 2 : The First Option, "Run with Sprinter" is used only when sprinter is installed. Sprinter is a plugin within HP which assists the manual testers to execute tests with advanced options and settings.

Step 3 : The Second Option, "Run with Manual Runner" is the option for executing tests manually. The manual runner window opens as shown below.

Let us now understand the functionalities in manual runner dialog.

• Begin Run - Kick starts the execution of Manual Tests
• End Run - User can exit the execution at any point by clicking on "End Run" button.
• Cancel Run - User can cancel the execution at any point in time.
• New Defect - A New Defect can be raised right from the Manual runner window
• OS info - Gives detailed information about the Operating System

Step 4 : Click "Begin Run" and the Manual runner pops up with all the manual steps as shown below.

Following options are available during execution.

• Add Step - Tester can add steps at runtime.
• Delete Step - Testers can remove a step at runtime if redundant.
• Cancel Run - The execution will be cancelled
• Pass Selected - The Selected Step will be marked as Pass.
• Pass All - All the Steps in the test will be marked as Pass.
• Fail Selected - The Selected Step will be marked as Fail.
• Fail All - All the Steps in the test will be marked as Fail.
• Parameters - Shows the list of parameters that was added as part of the test
• Attach to Step - Enables user to attach a file to a particular step
• Attach to Run - Enables user to attach a file on a test set level
• Add Defect - Testers can add a defect by selecting the step and clicking on "Add a Defect"
• Filter - Testers can filter based on the status like - completed, blocked etc.
• End Run - Even while execution is in progress, testers can end the execution.
• Description - Shows the description of that step.
• Expected - Displays the expected result of that step.
• Actual - Tester can fill in the actual result.

Step 5 : Raising Defects in just a click away while the execution in progress, which prepopulates the step details such as description and expected result which is very handy for testers and easy for developers to investigate. It saves a lot of time in posting the defect, however the details about the usage of defects will be dealt in defects module.

Test Results

After executing tests, testers can view the results in the "Test Runs" module which contains tabs which lets testers to analyze the results of test instance runs and test set runs.

Goto "Test Runs" in "Testing" Tab and the window opens as shown below:

Below are Features of Test Run Tab.

• Delete - Enables testers to delete a particular test Run and can be controlled by user previleges.
• Details - Upon opening the details tab the execution details of each step is shown.
• Continue Manual Run - Enables testers to continue with manual run if suspended inbetween.
• Goto Test Instance - This option takes to the test instance under test Lab module.
• comments - Allows testers to add comment to the test run.
• Report - Displays the details of the Run with steps and its status.
• Attachments - Enables testers to add attachments for that particular execution.
• Run ID - HP-ALM assigns a unique run ID(date-TimeStamp) automatically so that it can easily tracked.
• Exec Date - Enables testers to track the test execution based on execution date.
• Exec Time - Enables testers to track the test execution based on execution time.
• Host - Displays the host system on which the test was performed.
•