When I've done this before, we had a base test class which put everything in the same collection. That class implemented the IAsyncLifetime interface which reset the database and all that
Or 2. If your system is multi tenant, have each test run under its own user id or organisation id or whatever, so that they don’t interfere with each other, even when running in parallel
Either
1. Use collections to ensure the tests don’t run in parallel and have a common setup and reset method, using perhaps IAsyncLifetime on the base class
•Created by Luca | LeCarbonator on 11/13/2024 in #help
✅ Is it possible to access a Controller's URI at runtime?
^ that too, when I’ve deployed stuff like Grafana I’ve had to specify a domain in the config, so I assume they might be doing something like this for their redirects