Implement a user path
After recording your user path in Tricentis NeoLoad, you need to implement it to create realistic user behavior patterns for your performance tests.
To implement a user path, follow these steps:
-
Review the recorded user path structure in the Design section. Examine the containers and recorded requests to understand the captured user journey.
-
Organize your user path by creating logical groupings:
-
Create Transactions to group related pages as business functions.
-
Add Containers to structure complex workflows and reusable components.
-
-
Insert delays and think times to simulate realistic user behavior.
-
Configure variable extractors and correlations to handle dynamic data:
-
Identify dynamic parameters that change between test runs.
-
Create variable extractors to capture dynamic values from responses.
-
Use extracted variables in subsequent requests to maintain session state.
-
-
Check your user path by running a validation. Select Start Checking under the Run tab to verify that your user path works correctly and identify any issues that need resolution. To learn more, see Check a user path (opens in a new tab).
Use CheckVU for debugging
The Check Virtual User (CheckVU) feature runs a mock execution of your virtual user and displays detailed information about all actions and requests.
In case of issues, CheckVU also provides a list of errors and warnings with suggested solutions. You can use this list to identify and fixdesign issues with objects such as dynamic parameters and correlationss before running a full load test.
Use CheckVU regularly as you customize your user path to ensure all changes work correctly.
What's next
After implementing your user path, it's time to create a test!