There is a concern regarding test isolation in our current testing setup. Some tests may alter the database state, which can lead to interference between tests and unreliable results. To ensure proper isolation and prevent tests from affecting each other, we should consider using a temporary database for each test run or implement mocking strategies for database interactions.
Action items:
- Review current test setup for database state management.
- Investigate options for using a temporary database or mocking database calls during tests.
- Update test infrastructure to ensure tests do not affect each other's database state.
- Document the chosen approach for future contributors.
I created this issue for @ajwalkiewicz from #17 (comment).
Tips and commands
Getting Help
There is a concern regarding test isolation in our current testing setup. Some tests may alter the database state, which can lead to interference between tests and unreliable results. To ensure proper isolation and prevent tests from affecting each other, we should consider using a temporary database for each test run or implement mocking strategies for database interactions.
Action items:
I created this issue for @ajwalkiewicz from #17 (comment).
Tips and commands
Getting Help