Detailed Test Report Content

General Information

The General Information section includes administrative information in tabular form.

Administrative information includes the Silk Performer Version information, the project name, a description of the project, the date and time of the baseline test, the workload definition, the workload model, and the number of errors that occurred.

User Types

For each user type involved in the test run, a separate section is available with details on the measured response times. The following information appears in the summary line:

• Number of virtual users (one for a baseline test)
• Test duration
• Session time
• Session busy time
• Average page time
• Average action time
• The following numbers:
  • Transactions that were executed successfully
  • Canceled transactions
  • Failed transactions
  • Errors

The session time consists of the execution time of all transactions defined in the dcluser section of a test script, without the initial and end transactions. The session busy time is calculated as the session time minus think times, as the following example shows.

dcluser
  user
    Vuser1
  transactions
    TInit  : begin;
    T1     : 1; 
    T2     : 3;
    Tend   : end;

The session time is the average response time of T1 + 3 * average response time of T2. The session busy time is the same without any think time.

If you are satisfied with the results, you can set them as baseline results and save them for further processing, such as the calculation of the number of concurrent virtual users and the network bandwidth needed for the load test.

For each user type, detailed results are available in the following sections:

• Summary tables – Contains aggregate measurements of all virtual users in tabular form. The first table provides general information, such as the number of transactions that were executed and the number of errors that occurred. The remaining tables provide summary information that is relevant to the tested application type.
• Transactions – Displays the following aggregate measurements in tabular form for all transactions of a specific user type:
  • Transaction response time – Measured from the beginning to the end of the transaction, including all think times.
  • Transaction busy time – The transaction response time without any think time.
• Page and action timers – Displays the following summary measurements in tabular form for every accessed Web page:
  • Download time of the entire page
  • HTML-document download time
  • Server busy time
  • Amount of data downloaded with the page
  • Amount of data downloaded for embedded objects
• Web forms – Displays the following measurements in tabular form for every used Web form:
  • Roundtrip time
  • Server busy time
  • Number of HTTP hits
  • Amount of request data that was sent
  • Amount of response data that was received

If the results of an inspected load test are acceptable for use as a baseline, you can store them for further calculations and processing by clicking Accept Results. The results of tests with all user types involved are stored in the file <projectdir>\BaselineResults\baselineReport_<workloadname>.brp. You must define a separate baseline for every workload that is defined in your load test project. If you create a copy of a workload, the baseline results are also copied.