Currently, some of our CLI tests rely on a global configuration environment. This has caused integration test failures because multiple tests end up sharing the same configuration file and database.
As a temporary workaround, I ensured that those specific tests run serially. However, this is not a long-term solution.
We should instead configure the global testing environment—ideally using a temporary directory—so tests are fully isolated and we don’t have to worry about shared state.
Currently, some of our CLI tests rely on a global configuration environment. This has caused integration test failures because multiple tests end up sharing the same configuration file and database.
As a temporary workaround, I ensured that those specific tests run serially. However, this is not a long-term solution.
We should instead configure the global testing environment—ideally using a temporary directory—so tests are fully isolated and we don’t have to worry about shared state.