Run slowest tests first or provide a way to provide the order of tests

[flunderpero]

Clear and concise description of the problem

Jest runs the slowest tests first. That decreases overall runtime of our test-suite from ~90s to ~70s. In vitest the same suite always takes ~110s mainly due to the increased isolation (which is the greatest feature of vitest imo) but also because it so happens that the slow test files are started near the end of the run.

Suggested solution

Either implement Jest's approach and run the slowest test suites first or allow the user to specify the order in which tests are started. I would prefer Jest's approach.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sheremet-va]

I also noticed it, thank for pointing out. We may need to store previous tests results in a cache somewhere.