My application under test does not allow the same username to login twice at the same time. How do I run my tests with the same username and password

If your application does not allow concurrent login with the same username and password, you can add your test cases in an execution set and use chaining as below:

1. Hover over Executions > Execution Sets

2. Click Add and create a new execution set

3. On the Tests Data Selection tab, select your different test cases that use the same credentials

4. In the middle, click the icon highlighted below to select all tests

5. Once all test cases are selected, click Chain icon highlighted below

6. You will notice that your tests have been added to a single group. Every test case inside this group will execute in sequence (not in parallel) according to the order they were positioned in. This will ensure that your username and password will be used only once at a time and cannot cause any session expiring due to another test using the same user. 

7. You can drag and drop the tests to change the order if you like as shown below:

8. The name of the group can also be changed by selecting it and using the option highlighted below:

9. After saving your execution set, you can schedule your test to run automatically or directly run it in cloud by selecting it and clicking any of the icons in the toolbar.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Melnik, Vitaly (NIH/OD) [C]

    Would it be possible to run the same script with multiple data sets one after another one?
    Lets say we add the script to the chain. Now each script will be executed one after another one. But second script has multiple data sets selected, so it will be executed also multiple times. Currently, in this scenario execution is distributed among multiple VMs which brakes proper execution.

    0
    Comment actions Permalink
  • Avatar
    Joseph Hamdan

    Hi Vitaly,

    Apologies for delay in response. Would you please let us know if your chain was built around a dependency ? For example, concurrent login in is not allowed.

    Regards,
    Subject7 Team

    0
    Comment actions Permalink
  • Avatar
    Melnik, Vitaly (NIH/OD) [C]

    Yes, execution for the script with each test set option should finish before next option starts because concurrent login is not allowed. Hope it makes sense.

    0
    Comment actions Permalink
  • Avatar
    Joseph Hamdan

    Hi Vitaly,

    Thanks for confirming. Since chaining is only designed to work between each test case, we suggest an alternative which is to use a pool with only one VM. This way, only one test (one dataset selection) will execute at a time.

    Regards,
    Subject7 Team

    0
    Comment actions Permalink

Please sign in to leave a comment.