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 do the following.

  • 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, click the Quick Run button on the top of the Test Run. 

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

To use the Quick Run option for multiple test runs, you can do one of the following.

  1. Use the checkboxes to select the test runs from the Test Run grid of a release, cycle, or suite.  Then, click "Quick Run" from the top of the grid. 



    OR

    F
    rom the Test Run Data Query, use the check boxes to select multiple test runs and click the "Quick Run" option. 



  2. In the Test Suite Quick Run window, mark the overall status for each test run.  To quickly mark all test runs with the same status, you can select the check boxes, 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

Test Pad 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, click the Run button on the top of the Test Run.



To use the TestPad option for multiple test runs, use the check boxes to select the test runs from the Test Run grid of a release, cycle, or suite.  Then, click Run from the top of the grid. 

After you click Run, the TestPad is displayed in a separate window.

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 log back into qTest Manager, and repeat the above steps to launch the TestPad. 

The screen shot below displays numbers to show what you can do within the TestPad:

  1. Select Test Runs in the drop-down list to execute (if you selected multiple test runs to execute, they will display in the drop-down
  2. Click Forward or Backward icons to execute in order
  3. Click Load Last Run 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)
  4. View Test Case's DescriptionPreconditionNotes, and Attachments in Test Run Information section.
  5. Add Attachments for Test Case and Test Log separately in the Resources.
  6. Select overall Status for the Test Run.  OPTIONAL: If you want to quickly mark the same status (e.g., Passed) for all test steps AND the overall test run, you can click "Apply status to all test steps" after you select the test run status.  
    • HINT: Here you are marking the status for the test run, which is distinct from the status of each test step.  If a particular step fails, you may still decide to pass the test run itself. For example, if the test step is considered to fail due to minor cosmetic flaws, the overall test run can still be considered passed if you are testing for functionality.  In other words, there are no conditional rules built into the system that impact the overall status of the test run based on the test step statuses.  This is based on the tester’s discretion.
  7. Select Status for individual Test Steps.
    • Move your cursor into the Status cell of the test step.  Once you hover over this cell, the status drop-down list will display and you can indicate whether each test step passed or failed.

        
  8. Click the Bug icon to submit defect(s) for individual Test Steps.
  9. Click the Clip icon to add Attachments for individual Test Steps.
  10. Click into the Step Information cell in the Test Step row to view the test step's Description and Expected Result from the test step in Test Design.  In the 3rd cell of the Edit Test Step Information window, input the Actual Result of the test step. 
               
    • HINT: Clicking on the Step Information cell for steps that pass is optional.  You may decide that if the expected result occurs for a given step, it isn’t necessary to fill in the actual result in the Edit Test Step Information pop-up window.  To save time, you may wish to click the Step Information cell only if a particular step fails to provide more detail into why the step failed.
  11. Click Save to submit Test Result for Test Run 
  12. OPTIONAL: The Execution Time pop-up window displays.  You may click the Skip button if you wish to skip this step.  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 press the Save button.   For more details, see the article Time Tracking Settings.
  13. Once you reload the page, the details of this execution (including actual results and status for each test step), will be in the Execution History area of the test log page.

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 of Test Case in Resources.
  3. Click individual Test Steps to edit Step DescriptionsExpected Results, and Actual Results.
  4. Re-order Test Steps by clicking Move Up or Move Down icon in the Config column.
  5. Add/Remove Test Steps by clicking Add or Remove icons in the Config column.
  6. Add/Remove Attachments of individual Test Steps.

  

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.

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