Check a user path
Before you run a test in Tricentis NeoLoad, check your user path to identify and fix issues with dynamic parameters, variable extractors, and other design elements that might cause problems during load testing.
This topic explains how to check a user path before running your load test.
Before you start
Before checking a user path, make sure you have the following::
-
A recorded User Path that contains at least one action or request.
-
Access to the application you want to test.
Run the check
To check a User Path, follow these steps:
-
Select Start Checking under the Run tab in the menu bar, or select Check User Path button in the toolbar.
-
In the Check User Path dialog, select the User Path you want to check.
-
Select Start checking to run a mock execution of the virtual user.
If the check returns no errors, your user path is ready for the next step in the user path workflow. If any errors are detected, resolve them before moving on to testing.
Work with errors
If Tricentis NeoLoad catches any inconsistencies in the design, you'll see the Execution Sanity Check dialog. This dialog lists detected errors and warnings with suggested solutions.
While you're working on fixing the errors, keep this dialog open and select Refresh to update the error list. Continue fixing and updating until the user path runs without errors or warnings.
Common issues
Here are some common issues you might encounter when you check a Virtual User:
The Virtual User doesn't include any actions. To resolve this issue, add actions to the User Path or use a different Virtual User for your test.
The server generates links with dynamic parameters that change between test runs, such as /results?searchID=345365. To resolve this issue, convert the request to use a link extractor, or create a variable extractor to capture the dynamic value.
A request uses a variable that doesn't have a value. To resolve this issue, verify that your variable extractors run before the requests that use the variable, and check that the extraction patterns match the server responses.
Session IDs, tokens, or other values that the server expects don't match. To resolve this issue, identify where these values first appear in responses and create variable extractors to capture them. Then, use these variables in subsequent requests.
What's next
When you have an error-free user path, you're ready to, create populations to define how virtual users distribute across your user paths.