Design a test scenario

To work with tests, NeoLoad uses test scenarios within a test project. Test scenarios are recordings of a given web browsing sequence, which you can later configure for your testing activities. With the help of virtual users, NeoLoad tracks browsing actions and generates behavioral patterns called User Paths.

This quick start guide demonstrates how you can create your first test scenario in a new project.

Design a test scenario

To design a test scenario, follow these steps: 

  1. In NeoLoad, choose File > New to create a new test project.

    Note: The Project name can only contain letters, digits or underscore. Any punctuation characters, spaces or dashes are not allowed.

  2. In the project, click Start Recording. In the Recording dialog box, enter the name of the User Path and specify the conditions of the browsing sequence you are about to capture.

    You can then further configure conditions for your User Path in the Design tab of NeoLoad Controller.

  3. In the displayed Web browser, enter the URL of the test site. Browse as usual. NeoLoad records all your actions.

    Note: Before recording the scenario, it is recommended to close all HTTP client applications (other Web sessions, Twitter client, and so on). NeoLoad records all the HTTP flows going through the machine. It is necessary to close HTTP clients or define exclusion rules in NeoLoad to avoid unwanted requests in the recording.

  4. When recording (or after), you can create Transactions to organize the visited pages and structure your scenario as business transactions. Subsequently, you can configure them for reuse in other scenarios.

  5. Once you are done with the browsing sequence, click Stop Recording. The Post-recording Wizard opens. Follow the wizard steps to configure your User Path.

  6. Return to NeoLoad Controller and specify the running parameters of the new User Path in the Runtime Parameters area.

  7. To check the User Path — and correct errors or unexpected behavior —, choose Run > Start Checking > Start Checking. Double-check requests and responses and go through any potential errors raised by NeoLoad.

  8. Return to NeoLoad Controller and choose the Populations tab. This lets you manage User Path groups called Populations.

  9. Choose the Monitors tab to define the monitors of the servers hosting the tested application.

Learn more

For more information on test design, check out these topics: