If all requests pass verification, and the Verification Tree displays all green checkboxes, then your test case is configured and you can move on to the next step of configuring the load and running the test.
However, sometimes the session verification tree displays diagnostic messages. This means that some issues were discovered when a virtual user replayed the test case.
Different issues can impact test accuracy with various degrees, from an insignificant impact to total test failure. For example, if a virtual user sends a request to a static image without caching headers, the test's accuracy will be minimally affected. However, if the authentication process fails, then all remaining requests will not be authenticated and the test will be totally incorrect.
In order to address verification issues, try to find what is causing them, fix the problem and then verify the test case again. A solution to the problem depends on the type of message that you receive. In some instances, such as authentication failures, fixing an earlier issue will solve later ones. Therefore it is recommended that issues be addressed from the beginning of the test case to the end.
The table below lists the most frequent issues and gives some recommendations on how to resolve them.
|Session Status Type||Diagnostic Message Example||Possible Resolution|
|Error||Response Code 500 |
|Find and create missing parameter(s) as described below.|
|Warning||Response Code 401. |
The user is not authenticated.
|The replayed request was not authenticated. |
Check Test authentication settings.
If subsequent requests are authenticated,
this may be normal.
|Warning||Verified response code does not match the recorded response code |
Example: The verified response code is 302 and the recorded response is code 200.
|Find and create missing parameter(s).|
|Warning||Verified redirect URL is different than the recorded redirect URL.||1. If you are redirected to the same page but a different query string, this may be normal. |
2. If you are redirected to a different page, you most likely need to create a parameter.
|Warning||Verified response size is significantly different from the recorded response size.||Compare the recorded and replayed sessions. If the verified response is expected then ignore this warning. Otherwise, create a parameter.|
|Notification||Response Code 404. |
The resource is not found on the server.
|1. Add the missing resource to the server. |
2. If the resource is a static file (such as an image) that is not significant from a performance standpoint, delete this request from the test case.
|Notification||The first request in the test case contains an ASP.NET |
SessionId cookie. The beginning of the test case
may be missing
|This may be an indication that the beginning of the test case is not recorded. Re-record if this is true, otherwise ignore it.|
|Notification||The resource was cached during Test Case recording (response code 304) and not cached during replay (response code 200).|
This notification can be ignored. If you with to avoid it, consider:
- when recording a test case select browser Private Mode. See Recording with Web Browser
- or clear the browser cache and re-recording the Test.
- enabling cache control emulation in StresStimulus. See Test Case: Caching Rules
|Notification||The resource was not cached during Test Case |
recording (response code 200) and cached during
replay (response code 304).
|Disable cache control. See Test Case: Caching Rules|
One of the most frequent reason of load test errors is missing parameter(s). There are several methods of identifying and and creating missing parameters which are described in the next several subsections listed below.