Summary Report

• If a project suite or a project contains at least one test item marked as a test case in the Execution Plan editor.

• If the tests to run were specified by their tags.

• If a script test contains at least one test case marked by using the aqTestCase.Begin method.

• If your test run contains a BDD feature file or a BDD scenario.

• The name of the testing session (it can be the project suite name, or the project name, or the name of an individual test item, or the name of a script routine or keyword test, or a tag, or a tag expression).

• The number of:

  • Run test cases.
  • Passed test cases.
  • Failed test cases.
  • Test cases executed with warnings.
  • Rerun test cases (including detailed information about retries for tests ended with warnings or successfully passed).
  • Unexecuted test cases (if any). Test cases the execution of which was not started. This can happen if the project run was stopped on an error or if a feature that the project includes is not supported by the current set of the product’s modules and add-ons.

  And, a chart that shows a ratio among these tests.

• The test run duration.

• A chart that shows the statistics of the passed and failed tests and of the tests executed with warnings.

• The General section that shows the start time and end time of the test run. It also shows the name of the computer where the test was run and the name of the user account under which the test was run.

• A list of test cases executed during the test run. These can be:

  • The test cases specified in the Execution Plan editor of each executed project.

    If a test case is executed several times during the test run (that is, the Count column of the Execution Plan editor specifies a number other than 1 for this item), the summary report takes into account all the iterations.

  • The test cases you specify manually in scripts by using the aqTestCase.Begin method.

  • BDD feature files.

  • BDD scenarios (regardless of whether they are marked as test cases or not).

  • Tests that were selected to run by their tags.

  The report lists the test cases in the order of their execution. It ignores any parent-child relations between the test cases (if any).

  For each item, the report shows the following information:

  Column Name	Description
  Test Case	The name of the test case. It can be: The name specified in the Name column of the Execution Plan editor. The name specified by the aqTestCase.Begin method. The name of the test as it is specified in the Code editor (for scripts) or in the Project Explorer (for keyword tests). (Only when running tests that match a tag or a tag expression.) The name you specify by assigning a tag in a special format to your test. (Only when running tests that match a tag or a tag expression.)
  Project	The name of the project to which the test belongs.
  Start Time	The time when the test case execution started.
  Duration	The time it took to execute the test.

  To filter the test cases by their status, click the appropriate status in the list header.

  To jump to the detailed test log quickly, click the test name. If there were errors during the test case execution, it will jump to the first error. Otherwise, it will jump to the beginning of the test case.

• If there are errors in tests that are not included in the Summary report (they are not marked as test cases), the report will show a notification about it. You can click it to quickly open the detailed test log to view information on the occurred errors.

To work with the Summary report, you can use the following commands available on its toolbar:

Item	Description
Export Summary as JUnit	Exports the Summary report to the JUnit-style format and saves it to the specified XML file.
Export full log to	Exports both the Summary report and the detailed test log to the specified MHT file or HTML files.
Send via E-Mail	Exports both the Summary report and the detailed test log to an MHT file and sends it via email.
Print	Prints the Summary report.