Virtual User Validation¶
The virtual user validation tool helps you ensure that your Virtual User runs fine before starting a test. It is available in the right menu of the virtual user design view.
The following procedure explains how to run a Virtual User Validation:
- Select the region where to start the Virtual User (You can add your own private injectors in the Private Hosts page).
- Click on the Validate button,
- The Validate button is disabled and a progress bar is displayed. The virtual user check can be stopped any time while running,
- Wait a few seconds, while OctoPerf runs a single instance of the VU and records the requests sent, and the responses received.
In the interest of time, Think times are not replayed during a Virtual User validation.
Region is the geographical location where the virtual user profile instances are being executed. You can configure the browser settings by clicking on the Configuration button.
The sanity check is the first step of a Virtual User validation. This process scans your virtual user to check if anything can break its execution (i.e. missing files) or can make your load testing results hard to analyse (i.e. empty or unnamed containers).
It displays a table that lists all errors:
|Level||The error level: INFO, WARNING or ERROR, displayed as a colored icon.|
|Error description||A short message to help you identify the issue.|
|Button||A magnifier icon, you can click on it to be redirected to the variable or action that causes the issue.|
If any breaking error is detected (level ERROR, with an orange stop icon), the debugging of the virtual user is cancelled. You need to fix it before running the validation once again.
If there are no errors during this first step, OctoPerf runs one instance of your virtual user to debug it. You can then check the injector logs and compare the requests/responses to the record.
When the validation is started, a button with a file icon appears at the right of the Validate one: it opens a Logs panel.
When compared to the recorded requests / responses, VU Validation information lets you know if anything went wrong. To give you a quick access to this information, OctoPerf displays colored dots on the left of the VU tree nodes:
There are 3 colors a response can get:
- Green: The response is OK
- Orange: The response is KO
- Yellow: At least a children is KO.
In case one request has been executed several times, one KO over all the executions is enough to mark it as orange.
The following table indicates the situations considered as KO/Orange during a validation.
Each line represents the validate response for a category of response time. For instance
200 and similar response codes.
Unknown reponse codes refers to codes that are outside the list of standard codes.
Each column represents the recorded response code in a similar fashion.
|Validation code||No recorded||Recorded 2XX||Recorded 3XX||Recorded 4XX||Recorded 5XX||Recorded unknown|
During runtime, the responses will be evaluated as errors as if there was no recorded response. Please refer to the first column of the table in that case.
In case you are not happy with the colors you see in OctoPerf, you can use response assertions to change this behavior locally.
Compare to record¶
You can also compare recorded requests / responses to Validate VU ones for each HTTP Request Action, in their Check Request / Response tab.
If you want more details on how to analyze the errors, please check the error table report item page.
In case your HTTP Request Actions do not have recorded content, OctoPerf uses the response status code during the Validate VU process to know if an error occurred. 4xx and 5xx response codes are error codes. It is also very useful in this case to configure Post Processors, as response bodies and headers are handy to write regular expressions.