Menu

Executing Test Runs

There are several ways to execute tests run in qTest Manager. 

  1. Quick Run
  2. TestPad only
  3. TestPad + Desktop Explorer
  4. TestPad + Web Explorer
  5. Schedule Test Automation

Quick Run

As the name suggests, the Quick Run option is a fast way to mark the overall execution of the test run without filling in further details.  Quick Run allows you to:

  • Mark overall status of the test run (e.g. Pass or Fail)
  • Submit time tracking details: planned and actual time
  • Submit a defect

To use the Quick Run option for a single test run:

  1.  Select the Quick Run button from the top of the Test Run.

  2. In the Test Run Quick Run window:
    • mark the overall status of the Test Run (e.g. Passed)
    • enter the planned and actual time (optional)
    • submit any defects
    • Click OK to save and return to the Test Run page.

To use the Quick Run option for multiple test runs:

  1. Use the checkboxes to select multiple test runs from the Test Run grid of a release, cycle, or suite.  
  2. Select the Quick Run button from the top of the grid.
    execute_multiple_quick_runs.png
    OR

  3. From the Test Run Data Query, use the checkboxes to select multiple test runs and select the Quick Run option. 



  4. In the Test Suite Quick Run window, mark the overall status for each test run.  
    Hint: To quickly mark all test runs with the same status, you can select the checkboxes, select the status at the top of the grid, and then click Apply.  Once a status is marked for each test run, click OK and Refresh to return to Test Execution.

TestPad

TestPad Only

The TestPad is the recommended approach for executing test runs, as this option allows the tester to view and submit as much detail as possible.

To use the Quick Run option for a single test run:

  1. Select Run from the top of the Test Run.
  2. Select TestPad only.

To use the TestPad option for multiple test runs:

  1. Use the checkboxes to select multiple test runs from the Test Run grid of a release, cycle, or suite.
  2. Select Run from the top of the grid. 
  3. Select TestPad only.
  4. After you select Run, the TestPad is displayed in a separate window. For more details, read the Understand the TestPad section of this article.

IMPORTANT: If the TestPad does not display successfully, your web browser pop-up blocker may be preventing the TestPad from launching.  To proceed, adjust your browser settings to always allow pop-ups from your qTest URL.  When the browser settings are changed, you may need to refresh your browser or log out, then login to qTest Manager, and repeat the above steps to launch the TestPad. 

TestPad + Web Explorer

A test run can be executed using Web Explorer, which is a browser plugin that can be installed on Mac, Chrome or Firefox.  

IMPORTANT: To use this function, you must have Create Session permission to execute a test run.

  1. To execute with Web Explorer, navigate to a test run page and click on the drop-down arrow next to the Run button.  Select the TestPad + Web Explorer option, which will launch both windows.
  2. If you do not have the browser plugin installed for Web Explorer, the following warning is displayed. If so, go to the qTest Resources page to download Web Explorer for your browser (Chrome, Safari, or Firefox).  
  3. Make sure your application under test is open in the same browser as qTest Manager and that Web Explorer is installed in that browser so that it can record the activities on your application.  
  4. In the Web Explorer pop up window, you can modify the Session name and enter a Description. Click the Start Session button.  The product will record your activities within this browser to capture evidence of what you are testing.  An indicator light blinks in the top right of the browser header to indicate the session is being recorded by Web Explorer.  
  5. To stop the session recording, click the Stop button.   A new tab automatically opens that shows the screenshots captured during the recorded session. Save the recording and close the Session page.
  6. Return to the TestPad window and fill in relevant information for your test execution, including whether the test run passed or failed.
  7. Click the Save button to complete the execution.  Return to the test run page and click the Reload button.  

On the Test Run page, you can see evidence of this execution in two areas:

  • Execution History tab shows the test log details from the TestPad, which shows the status of the test run and test steps

  • Sessions tab shows the recorded session from Web Explorer. Click on the Session ID hyperlink to be directed to that Session page, where you can see the recorded steps, screen shots, and environment. From this page, if you click into the Linked Objects section, you can see the Test Run, as well as the original associate test case, and any linked requirements or previously linked defects.

Test Pad + Desktop Explorer

A test run can be executed using the Desktop Explorer which can be installed on Windows.  If you would like to use Explorer to execute test runs, we recommend using Web Explorer instead. 

IMPORTANT: To use this function, you must have Create Session permission to execute a test run.

  1. To execute with Desktop Explorer, navigate to a test run page and click on the drop-down arrow next to the Run button.  Select the TestPad + Desktop Explorer option, which will launch both windows. 
  2. HINT: If you do not have Desktop Explorer installed on your machine, the following warning is displayed. If so, click the link to download Explorer.  


  3. When prompted to open Explorer, click the Allow button.                                                                  
  4. In the Desktop Explorer pop up window, you can modify the Session name and enter a Description. Click the Start button.  

  5. To stop the session recording, click the Stop button.   A new tab automatically opens in your browser that shows the screenshots captured during the recorded session. Save the recording and close the Session page.
  6. Return to the TestPad window and fill in relevant information for your test execution, including whether the test run passed or failed.
  7. Click the Save button to complete the execution.  Return to the test run page and click the Reload button.
  8. On the Test Run page, you can see evidence of this execution in two areas:
    • Execution History tab shows the test log details from the TestPad, which shows the status of the test run and test steps

    • Sessions tab shows the recorded session from Web Explorer. Click on the Session ID hyperlink to be directed to that Session page, where you can see the recorded steps, screen shots, and environment. From this page, if you click into the Linked Objects section, you can see the Test Run, as well as the original associate test case, and any linked requirements or previously linked defects.

Understand the TestPad

The TestPad window contains 5 tabs across the Information bar that allow you to record detailed information for test steps, view the test case details, insert/view attachments, include notes, and record time tracking. 

new_test_pad_basic_screenshot.png

TestPad Header

The TestPad Header provides information about the Test Run you are about to execute. Including the following:

  • Test Run ID
  • Test Run Name
  • If you are executing multiple Test Runs, you can select the down-arrow to the right of the Test Run name and all of the selected Test Runs will display in the drop-down list for easy navigation.
  • You can select the Forward or Backward icons to execute the Test Runs in order.
  • Select the Load Last Log button to view the most recent execution result of the Test Run. (This can be a helpful way to identify test steps that previously failed so that you can pay closer attention during this execution.)

test_run_hints.png

Execute Steps Tab

The Execute Steps Tab is where you will find information for the Test Case and record results, statues and defects for Test Steps. You can display up to 200 Test Steps on one page. A rich-text editor is available in the Test Step fields to provide formatting options such as bold, underline, and text color. Select the ‘A’ icon to display the rich-text editor.

Test Steps Column Information:

test_step_columns.png

  • Checkbox- allows you to select multiple Test Steps to bulk assign a status
  • Step#- displays the number associated with the Test Step
    Note: Precondition is listed as Step#0. Precondition will display when entered on Test Design, or you can insert add-hock here.
  • Attachment (Clip icon)- allows you to add an attachment for the individual Test Step
  • Description- description of what the Test Step is accomplishing
  • Expected Result- description of what should happen when the Test Step is executed
  • Actual Result- description of what does happen when the Test Step is executed.
    HINT: Entering the Actual Result for Test Steps is optional.  You may decide that if the expected result occurs for a given step, then it isn’t necessary to fill in the Actual Result. To save time, you may wish to enter details in the Actual Result cell only if a particular step fails to provide more detail on why the step failed.
  • Status- drop-down of available statuses you can individually assign to a Test Step
    • Hover over the Status cell of the test step and the status drop-down list will display. Here you can indicate whether each test step passed or failed.
      test_step_status.png
      HINT: Select the checkbox for each Test Step to bulk edit the same status for multiple Test Steps. Click the Select button to display the Status drop-down. Choose the appropriate status and select the Mark Selected Steps button. The Test Steps you chose previously will all receive the same status.
  • Bug- hover text displays the option to submit defect(s) for individual Test Steps
  • Action- hover text displays the options to reorder, add new, or delete the Test Step

Set Status and Submit Defect for Test Log

After you have marked the execution status for the Test Steps, you can set the status of the overall Test Log in the Set Status field, by clicking the Select drop-down.

Set_status_of_test_run.png

In addition to being able to submit defects for a Test Step, you can also submit a defect for the overall Test Log. Do this by selecting the Submit Defect button. Once the defect is submitted, a defect count will be visible in parentheses. For more information, read the Submit Defects in Test Execution article.
submit_defect_button_for_test_run.png

Test Case Details Tab

The Test Case Details tab is read-only and provides information that is entered in Test Design.

Attachments Tab

The Attachments Table and Attachment Preview provide you with additional information.

The Attachments Table provides the following details:

  • Name- the name of the attachment
  • Uploaded by- the user that uploaded the attachment
  • Date- date of upload
  • Type- the type of attachment
    • Test Log-attachments for this specific 
    • Test Case-attachments uploaded from Test Design
  • Action- provides a delete option

The Attachments Preview allows you to preview the attached image/file in the bottom panel by selecting the attachment name in the Attachments Table. Alternatively, you can select the backward and forward buttons to navigate through the available attachments.
Note: A PDF nor Excel file will display the image in preview mode. You will need to download the .pdf or .xls to view.

attachments_tab.png

Notes Tab

The Notes tab contains a Text field with a rich-text editor to allow you to document information regarding the Test Run. Notes entered here will be seen on the Test Run page in the Test log Details section of Execution History. A date/timestamp along with the user who entered the note is also displayed.

Time Tracking Tab

The Time Tracking tab allows you to manually track your planned time and the actual time spent executing the Test Run. Upon saving the Test Pad, a Time Tracking dialog will display with an auto-calculated execution time based on your start and end time. You will have the ability to modify the auto-calculated value.

The auto-calculation is in addition to being able to manually enter the planned and actual time. If you have logged your execution time on the TestPad in the Time Tracking tab, the manually entered values will override the auto-calculation.

Saving your Test Log

  1. Once you have finished your execution, you will need to save the TestPad.
  2. The Execution Time widget displays with an auto-calculated execution time based on your start and end time. Select Save. You can modify the auto-calculated value.
  3. (Optional)  If you wish to skip this step you may, by selecting Skip.  
  4. In the Planned Time field, enter the number of minutes you expected to take to execute the test run.  In the Actual Time field, enter the number of minutes it took to execute the test run.  Then Save. Manually entered values will override the auto-calculation.  For more details, see the article Time Tracking Settings.
  5. When you close the TestPad window, the Execution History area of the Test Run page will auto-refresh so the details of this execution (including actual results and status for each test step), will display.
    Important: If you are in the middle of making changes to any Test Execution properties and have not saved, and you close a TestPad, the background page will not refresh until you confirm you want to save your changes.

Edit Test Case during Execution

Sometimes when you're ready to execute the test run, you may notice that the test case needs to be changed as well. For example, the test case may be missing some important test steps or you may need to modify the Precondition. If you have the Approve Test Case permission, you can make changes on the Test Run during execution (from the TestPad), which will automatically update the corresponding Test Case as a newly approved version in Test Design. This functionality will save you time instead of requiring you to update the Test Case in Test Design first then relaunch the TestPad.

In the TestPad, you can:

  1. Edit Test Cases' Description and Precondition.
  2. Add or remove Attachments.
  3. Click individual Test Steps to edit Step DescriptionsExpected Results, and Actual Results.
  4. Re-order Test Steps by using the Move Up or Move Down icon in the Action column.
  5. Add/Remove Test Steps by selecting the Add or Remove icons in the Action column.
  6. Add/Remove Attachments of individual Test Steps.

Tips in Test Execution

Execute Approved Test Case

The Execute Approved Test Case pop-up may be displayed if the most recent version of the test case has not been approved in the Test Design module.  If you have permission to approve test cases, you can select the latest version of the test case, so that you can approve it and select to execute at the same time.  If you do not have approval permission, you can only execute the latest approved version (which may be outdated).  Once you select the test case version to execute, click the OK button.

HINT: You can also specify the test case version to execute in advance by selecting the Test Case Version field on the Test Run (and saving) before you click the Run button.  For more details on test case versioning and approval, see the article: Create, Edit, and Approve Test Case.

Default Execution Mode

The default execution mode will be TestPad only, but you can change the default execution mode to one of the other options: TestPad + Desktop Explorer or TestPad + Web Explorer by clicking the drop-down arrow next to the Run button.  After you select a different execution mode, the default is updated so that the same mode applies the next time you click the Run button. 

NEXT STEPS:  

See the following articles.

Subscribe To Our Blog
Powered by Zendesk