test: implement per-test isolation for integration tests #343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Implements Option A variant (per-test reset) for issue #335, providing true test isolation while maintaining acceptable performance.
Changes
tests/fixtures/services.py: Added
ServiceManager.reset_test_data()methodtests/integration/api/test_assignments.py:
tearDownClass()totearDown()setUp()(required because reset clears credentials)test_00_*prefix fromtest_list_assignments_emptyTest Results
test_00_*prefixes remaining in codebasePerformance Impact
Minimal: ~0.04s increase for 12-test suite (0.25s → 0.29s)
reset_test_storage()is cheap (closes/reopens SQLite connection, clears dict)Usage Pattern for Other Tests
Trade-offs
setUp()test_00_*naming hackFixes #335
🤖 Generated with Claude Code