Test Recorder Report



Analytics provides a detailed view of execution results. Users can study and analyze the executions by looking at the different statistics like Total Test Suites, Total Test Cases, Total Passed, Total Failed, Total Skipped, and Total Duration of the test run.

QAS Reports are available under the Analytics menu.

Test Recorder Report is generated for test suite execution for web and mobile web carried out through the Test Recorder section of QAS. Users can upload test results report directly to QTM/QTM4J. 

Users can drill down to the details of individual test suites to get details of the Environment and test cases. Currently, QMetry Test Management and Jira can be integrated as defect management to log issues from Test Reports.

Execute Test Cases

Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QAShelp/pages/915341379 for more details.

View Test Recorder Report


  1. Open the Analytics menu on the menu bar.

  2. Select Test Recorder Report.

The Test Recorder Report opens.

The report can be viewed in: A. Tabular View or B. Graphical View.


A. Tabular View

The Summary view of the report displays the count of test suites, test cases and execution statistics. Click on the Test to view more details for the test suite.

The report displays the Environment and test details of the test suite that has been executed.

Expand the Environment Information pane to view details about Execution System, Framework version, Desired Capabilities, Actual Capabilities, Run Parameters.



Click on the failed test to view its detail and analyze the problem.

Expand the test case pane to view details of Check Points, Step Time Analysis and Details.

You can apply a filter on - test case execution status, Configuration and Test to view desired details in the report.

Analyze Failed Executions

Check Points

Open the Check Points tab to view the check points of the failed test.

You can verify the operation that is performed during the test.


Step Time Analysis

The graph in the tab displays the execution time of each step in the test case.

The legends include Threshold and Duration.

  • Duration: It is duration time taken for executing a single test step.

  • Threshold: In QAF and Cucumber frameworks, users can specify the threshold value to each step. It is like the acceptable defined limit. If the time of execution increases the threshold value, that step will be marked as per the legend. For example, "Login" step is set with a threshold of 2 seconds. Now it takes 5 seconds for execution, then the “Login” step will be marked as Threshold.



The tab displays test case details like - Author who wrote the test case, Description of test case, test case Reference path, Start Time when test case execution started, End Time when test case execution ended, and the actual execution time of the test case.


Log Defects to QTM/Jira

QMetry Test Management can be set as Default to log issues. Refer to Integration with QTM.

If Jira is integrated with QAS, then issues can be logged into Jira when test cases fail. Refer to Log Issues in Jira.

If both integrations present in QAS, then priority will be given to QMetry Test Management and issues will be logged into it.



Upload Test Results to QTM/QTM4J

To upload the test execution to QTM/QTM4J click on the Upload button at top right and select the integration system you want to upload the result to.


B. Graphical View

To view the graphical presentation of the report, click on the graph icon at top right.

Export Test Recorder Report in PDF

You can export the report in PDF format to keep it handy for quick reference. It helps to share the report with other users who do not have access to QMetry Automation Studio.

To export the report, click on the PDF icon at the top right corner.

The exported PDF looks like the below image.

If a bug is raised through report, the bug link is also included in the exported PDF.