Post-recording wizard
After you finish recording a user path, Tricentis NeoLoad opens the Post-recording Wizard. This feature helps you configure the user path before you run any tests by excluding unnecessary servers, detecting and correlating dynamic parameters, setting think times, and configuring virtual user authentication.
Exclude servers
This step displays all hostnames and IP addresses that Tricentis NeoLoad captured while recording the user path, grouped by domain names.
To exclude traffic from hosts that aren't part of your testing scenario, follow these steps:
-
Review the hostnames in the tree.
-
Clear the checkboxes for hostnames that aren't part of the application you want to test.
-
Enable Add unselected host names to the recording exclusion list to instruct to ignore these hostnames in all future recordings.
Dynamic parameters
This step helps you detect and correlate the dynamic parameters generated by the server. These parameters often change between test runs and require variable extractors to work correctly.
Enable Use Framework rules to handle these cases automatically.
Framework-based parameters
If your application uses push or WebSocket technology, here's how Tricentis NeoLoad correlates the dynamic parameters:
-
Push application: For web applications that use push technology, Tricentis NeoLoad creates advanced configuration for supported frameworks.
-
Message mapping: For WebSocket applications, Tricentis NeoLoad searches for WebSocket message mapping in recorded requests and automatically configures the user path.
Generic dynamic parameters
Enable Search for generic dynamic parameters to have Neoload identify form or request parameters that must be extracted from server responses during the test.
Think time between pages
Think times simulate the pauses that real users take when they read and interact with pages.
Choose one of these options:
-
Use recorded think times: Keep the actual delays that occurred during recording.
-
Override think time for all pages: Set the same think time for all pages in the user path.
Authentication
This step lets you configure how virtual users authenticate, if its applicable to your user path.
Basic, Digest, NTLM, or Negotiate authentication
Choose how virtual users authenticate:
-
Use the recorded account: All virtual users use the same account you used during recording.
-
Use multiple accounts: Each virtual user uses a different account. Neoload gets the account data from a list of static values that you can enter directly or import from a CSV file.
Form-based authentication
When Tricentis NeoLoad detects a form with at least one text field and one password field, the post-recording wizard displays authentication forms. Select the forms that represent authentication, then decide to use a single account or multiple accounts.
What's next
After configuring your user path with the post-recording wizard, design your user path to add logical actions and refine the recorded interactions.