Page tree
Skip to end of metadata
Go to start of metadata

Test progress elements are located on the toolbar and in the Test Progress Panel

Toolbar Elements:

1. The Progress bar displays the test’s general progress status (a). A load test typically consists of 2 main phases:

      • Running the test by specified time, number of iterations or reaching maximum users.
      • Waiting for iterations to complete or issued requests to come back.

The progress of the each of the phases is displayed in two separate progress cycles from 0 to 100%. The name of the phase (b) is displayed on the left of the progress bar as follows.

    • On the first phase:
    • Running steady load by time
    • Running steady load by iterations
    • Running step load by time
    • Running step load by iterations
    • Running step load to max VUs
    • On the second phase:
      • Waiting for responses
      • Waiting for Iterations

      Info: The progress is also displayed in the program’s taskbar icon as a colored background wave.

 

2. The Health Monitor (c) monitors the StresStimulus test machine and alerts when it is approaching its capacity limit. This helps to avoid test machine overload in order to sustain high test accuracy. The following color coding is used:

      • Green: Normal. CPU Utilization is under 85%.
      • Yellow: High Load. CPU utilization is 85-95%. Metric accuracy can be impaired.
      • Red: Overloaded. CPU utilization exceeds 95%. Metric accuracy will be likely impaired. Stop unessential processes or reduce the number of VUs.

 

Test Progress Panel:

3. Test progress panel display the following parameters:

ParameterDescription
Time The time elapsed from the beginning of the test
 Users

The number of instantiated and active VUs, iterating trough their respective test cases. Some VUs can complete the test earlier than others and become inactive. VUs which completed all their iterations before the test ends are excluded from the active user count. If the test is configured to complete only after all VUs complete their iterations, then the VU count may go down before the end of the test.

 Iterations Started The number of started test iterations
 Iterations Passed The number of Iterations in which all responses were received
 Iterations FailedThe number of failed (aborted) iterations
 Requests Sent The number of issued requests
 Requests Pending The number of issued requests, for which responses are not received yet.
Responses OKThe number of received responses excluded errors and timeouts
 Errors The number of errors
Timeouts The number of timeouts
SQL CE Capacity used

(Displayed only if Data Storage is Embedded SQL Server CE)The percentage of the 4 GB storage limit used to store test data accumulated up to this point.

If using SQL CE and your test is reaching capacity limit, learn how to Reduce Test Storage Use.

Tip:  Requests Sent =  Requests Pending + Responses OK + Errors + Timeouts

Note: The test log is updated in batches with a 60-90 second delay.

Info: The full list of parameters in the test metric grids is provided in the User Interface Reference-> Runtime Dashboard.

  • No labels