- Comparing results among runs
To analyze the difference between two or more reports, you can compare them. For example, to analyze the performance of the application at different time slots or different milestone builds, you can compare two runs.
- Comparing schedule stages
When you are running a schedule, in this context, is used to refer to both VU Schedule and Rate Schedule that contains stages, time ranges are automatically created for each stage. You can view a report that compares these stages, and you also can set preferences to display the report automatically at the end of a staged run.
- Comparing results from various regions or agent locations
When you run a schedule that includes agents from different regions, use the Web Analytic reports to compare the performance data from these regions.
- Generating functional test reports
You can generate functional test reports of your tests, which summarize the pass or fail verdicts of elements in the test log. Functional reports are generated from the test run as HTML files that use predefined report designs.
- Publishing test results to the server
The test results indicate the quality of the application under test. Different stakeholders might want to check the quality of the application but do not have the desktop client installed. As a desktop client user, you can publish test results to IBM® Rational® Test Automation Server so that others can view them from the web browser.
- Publishing specific results to the server
If you have a single test result or multiple test results that are not published to IBM® Rational® Test Automation Server, you can publish a single or all of them simultaneously.
- Customizing reports
You can customize reports to specifically investigate a performance problem in more detail than what is provided in the default reports.
- Export test results
You can export the test result in different formats to share it with different stakeholders.
- Viewing response time breakdown
You can do detailed analysis of the response time to find bottlenecks in the HTTP traffic of the application.