> **Justification**
Writing tests can be hard and complicated sometimes, and state may accidentally carry between executions; by running each test twice, random-sorted per test module (which would also be random-sorted per project), the test engine could potentially detect and report such problems. This could help our users write better unit tests for their code.

**Description**
When the state of a test is "unknown" and this setting is enabled, the test engine would execute each unit test t

> Follow-up questions (via LinkedIn/InMail):

---

I leave here my answer to Ben's reply to my post in case you could somehow paste it into the comments section:

"Thanks a lot for your time and explanations! It has taken me a couple of hours to understand your explanation, read through the post again and write this answer. I hope it's up to yours!

Let me give you some background and why it's still a bit difficult for me to properly understand some concepts, because I'm afraid I'm stil

> Really interesting idea/feature. Wondering if in addition to 'random', offer 'reverse order'. Simply running the default test sequence in reverse would simplify the user's troubleshooting efforts because the sequence is still deterministic and easily repeatable - my suspicion is that reversing the order would uncover most of the issues of 'state retention/leakage'.

Further, if a randomized test sequence gets a different result than a deterministic sequence, it would seem the user may be

> **Justification**
Exporting modules to a location other than where the workbook is saved becomes tedious when you have to navigate there every time.

**Description**
Cache export directory path after initial export to use as starting point for subsequent exports.