One of the most common scenarios of web application load testing includes a login step. To implement the test, LoadView will simulate the specified number of virtual users logging into the target web resource. To pass through the login process, a login and a password that were provided during the EveryStep script recording process will be used.

However, some web applications do not support concurrent login. This means that only one user with the same credentials can log into an account and perform specific actions at a time. The web application will accept the first user login and deny all further login attempts with the same credentials until the first session is finished. By default, LoadView uses the same credentials for all concurrent users in the test.  That being said, the conventional LoadView approach will result in errors during the login step.

To test web applications that support multiple user concurrency, the LoadView platform supports simulating unique concurrent user sessions on the target resource. The set of unique user credentials can be added to a CSV file, and then attached to the test scenario. LoadView will randomly choose a login/password pair from the file while each user session is generated. To manage the credentials, follow the guideline from Setting up Dynamic Variables for Web Application Load Test.

Note that dynamic variables from a CSV file are not used for device validation. Validation is executed using the initial login parameters provided in the recorded script. Given this, in case a new validation has been started before the previous session ended, the validation error may occur due to concurrency inconsistencies. See how to run validation with unique context parameters in the Validation of Load Test.