After the verification process is over, LoadComplete displays summary information on the verification results in the Report panel. You can also open the Details panel to view detailed information on the requests simulated during the playback and on the responses received from the tested server.
If the test log contains neither warnings, nor errors, the verification is considered passed. Otherwise, you need to find the reasons of the verification failure and fix the problems that cause them.
LoadComplete reports warnings if the received response code differs from the response code recorded during scenario recording. To resolve the problem:
Try to find the cause of the incorrect response manually, fix the problem and then verify the scenario again.
Configure LoadComplete to treat the received response code as expected. To do this, in the test log, select the request to which the tested web server sent the problematic response, right-click it and then click Mark Received Response Code as OK. Then, verify the scenario again and make sure that the response code is treated as the expected one.
Re-record the scenario and try to verify it again.
For more information, see Resolving Warnings.
Usually, LoadComplete reports errors in the following situations:
If LoadComplete failed to send a request (or requests) correctly. This can happen, if, for example, the connection to the tested server was broken during verification. To solve the problem, make sure that your load station can access the tested server and try to verify the scenario or test again.
If the measured page load time, time to first byte, or duration metrics violate the service level agreement criteria you set for your test or for individual pages, requests or other operations in scenarios.
This may indicate that there are server performance issues, or that the service level agreement criteria in your test are too strict. In the latter case, you can avoid the problem by modifying the criteria of your test or scenario.
A validation rule you set for your scenario has failed.
This may indicate that the server malfunctioned or that you need to correct the comparison conditions.
For more information, see Resolving Errors.