I am part of a UX team running multiple tests every fortnight. As our capacity to launch tests increases, so too does the risk of tests overlapping. We were excited to discover the "1 user, 1 test" feature which would mitigate the risk of overlapping tests contaminating data. However, we've discovered this feature makes it difficult for us to QA our tests.

As we are on the website all the time QA'ing and checking in on tests, of course myself and my colleagues are all bucketed into past or current tests, which means we are automatically rejected from test targeting for any test we are trying to QA with this feature turned on.

As a workaround, we can QA our tests and then afterwards turn on the "1 user, 1 test" feature. However, that prevents us from QAing and launching any future tests while the test requiring this feature is switched on. As we would only want to use "1 user, 1 test" when we are running many tests, this seems to make the feature a bit redundant. We can do manual QA but that is cumbersome.

It would be great if the QA assistant could override "1 user, 1 test" settings so that we can have this feature running, have interacted with other current or recent tests, and still be able to use the QA assistant for new tests.