Home
Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
Evaluating results in web analytic reports
After the test run, evaluate the results in the web analytic reports. Web analytics collect data using new technologies thereby providing better user experience.
Viewing response time breakdown
You can do detailed analysis of the response time to find bottlenecks in the HTTP traffic of the application.
Viewing page response time contributions
You can view the response time contributions for individual pages to determine how much time was actually taken by the page to load and the time taken for the connection to go through and the delay on the client side of each page.

Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
- Evaluating results in web analytic reports
  After the test run, evaluate the results in the web analytic reports. Web analytics collect data using new technologies thereby providing better user experience.
  - 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 indicates the quality of application under test. Different stakeholders to the application might want to check the quality of application but do not have the workbench or desktop client installed. As a desktop client user, you can publish the test result to HCL OneTest™ Server so that others can view it from the web browser.
  - 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.
    - Viewing page element responses
      You can view the response times for individual page elements in reports, to determine which elements are the slowest.
    - Viewing page response time contributions
      You can view the response time contributions for individual pages to determine how much time was actually taken by the page to load and the time taken for the connection to go through and the delay on the client side of each page.
    - Viewing response time breakdown data
      In addition to viewing page element and page response time, you can do further analysis to view the response time data for each method.
- Logs overview
  HCL OneTest™ Performance uses logs to store different types of information, which you can use to determine the reason for a test failure.
- Reports and counters
  See the description of the counters for all of the performance reports.

Viewing page response time contributions

You can view the response time contributions for individual pages to determine how much time was actually taken by the page to load and the time taken for the connection to go through and the delay on the client side of each page.

Before you begin

Because page elements can be returned in parallel from the server under test, the page response time is not necessarily the sum of the page element response times. Client delay and connection time also contribute to page response time. The page response time can be greater than the sum of the page element response times if, for example, a lengthy connection time adds a delay. Connection time includes the time required for Domain Name Services (DNS) lookups. Conversely, the page response time can be less than the sum of the page element response times if multiple page elements are returned in parallel.

Procedure

Open the web analytics report.
On the Page Performance report, click a page (represented by a bar) and click Page Response Time Contributions.
The Page Response Time Contributions report shows the average response time taken for Connection Time, Client Delay Time, and Page Element Response Time.
To return to the original report, click the Page Performance link in the breadcrumb.