[FEATURE REQUEST] Control order in which Unit tests are executed

Describe the bug I have multiple unit tests in a test suite and these need to be in a certain order, so have information available in the next request. When I execute this with the cli tool, this doesn’t follow the order from the GUI.

I know in theory unit tests shouldn’t depend on each other, but with the current way of running multiple requests, you have no clear view which requests are bering executed due to the use of the name.

To Reproduce Steps to reproduce the behavior:

1. Go to ‘Test’
2. Create a new test suite
3. Create 4 or 5 tests with a incrementing number in it’s name
4. Execute the test-suite
5. See different order of unit tests

Expected behavior The order with the CLI should be the same as in the GUI.

Screenshots

  General
    ✓ Returns 200 (1585ms)
    1) Returns 200
    ✓ Returns 201 (305ms)
    2) Returns 200


  2 passing (2s)
  2 failing

  1) General
       Returns 200:
     Error: No responses for request

  2) General
       Returns 200:
     Error: No responses for request

The third test (201) should have run second.

Desktop (please complete the following information):

• OS: macOS 10.15.6
• Installation Method: dmg and yarn
• App Version: 2020.3.3 and 2.2.22

Additional context Add any other context about the problem here.

[palevi67]

To me it would be a great if:

1.- Insomnia-cli run tests sequentially and in a known order (as insomnia now do) 2.- Insomnia allows to manually reorder tests

This would make test configuration much simpler, reducing the need to deal with javascript code and obscure request ids.

Maybe what insomnia calls “test” could be renamed to “test step” or “api call” or something similar, and what insomnia calls “test suite” could be renamed simply a “test” … what do you think?

[Neko-Design]

Hey All, this one is a critical one for my current case as well, where we have an ordered flow to validate each step of an onboarding api, something like:

1. Create Account
2. Send validation email
3. Update Account
4. List account resources
5. Delete account

Where each call needs to be made in sequence as running the steps out of order wouldn’t work, so we need guaranteed ordering in some way.