Test Run History

Go to Test Management > Run History.

Here, you will see the list of all runs across all team members, test sets, and tests:

Click the image to enlarge it.

The test run history is color-coded:

• Green for passed;
• Red for failed;
• Black for all other statuses.

From here, you can go into details of each test run.

Click buttons in the Actions column to perform various actions with the runs stored in QAComplete:

• Printer Friendly – Opens a run in an easy-to-read printable form.

• View Run – Opens the test run results. You can view the results of each test and of each test step.

• Restart Run – Starts a new run with the same parameters used in the original test run. This way, you can rerun your test.

  Note:

  This option is active for failed tests only. If a test set run includes failed tests, they will have the In Queue test status. The other tests will keep their status they had in the original run. If a test run failed, all its steps will have the In Queue status.

• Delete – Deletes a test run.

  When you delete the test run history, the deletion will clean up and recalculate the average run time for the tests and test sets involved. If you are deleting the most recent run for a test set, it will also clean up the last run information on the set and on the tests.

To go through the run history for a specific test:

1. Go to Test Management > Test Library.

2. Move the mouse cursor to the row of the test that contains the results you want to view, then click the Edit button that appears to the left.

3. Switch to the Run History tab.

Click the image to enlarge it.

Here, the following actions are available to you:

• Printer Friendly – Opens the test run in an easy-to-read, printable form.

• View Run – Opens the test run in the Test Runner.

• Restart Run – Starts a new run with the same parameters used in the original run. This way, you can rerun the test. If the test was run as part of a test set, the entire test set will be restarted.

  Note:

  If a test failed during the original run, all its steps will have the In Queue status. Otherwise, the steps will keep the status they had in the original run.

If the test was run as part of a test set, you will see the full view of the test set, where you can go to each test in the run and to the test steps to view the results.

To go through the run history for a specific test set:

1. Go to Test Management > Test Sets.

2. Move the mouse cursor to the row of the test set that contains the results you want to view, then click the Edit button that appears to the left.

3. Switch to the Run History tab.

Click the image to enlarge it.

Here, the following actions are available to you:

• Printer Friendly – Opens the test set run in an easy-to-read printable form.

• View Run – Opens the read-only version of the Test Runner.

• Restart Run – Opens a new instance of the Test Runner with the same parameters as those used in the original test set run, which you can use to run the test set once again.

  Note:

  This option is active for failed tests only. The failed tests will have the In Queue status. The other tests will keep the status they had in the original run.

When you submit automated tests, the test runner will post the top level of details from the automated test results. From the run history, you can go to the detailed results:

• If you use TestComplete, ReadyAPI, or SoapUI to run automated tests, the Test Runner will post the appropriate log file. Open the attached log file or download the file and view the detailed test results.

  Note:

  If you use Test Agent version 2.1, it exports TestComplete test logs to an HTML file. You can view them in any supported web browser. Otherwise, the test logs are stored in an MHT file. You can view them in Internet Explorer only.

• If you use NUnit to run Selenium automated tests or unit tests, the Test Runner will post an NUnit test project log file. Download the file and view test results on your computer.

• If your Selenium automated test or unit test fails, the Test Runner will post the console output of the appropriate unit testing framework (JUnit, TestNG, or NUnit) as test step results.