mirror of
https://github.com/azaion/ai-training.git
synced 2026-04-23 03:06:35 +00:00
Oleksandr Bezdieniezhnykh
142c6c4de8
- Replaced module-level path variables in constants.py with a structured Pydantic Config class. - Updated all relevant modules (train.py, augmentation.py, exports.py, dataset-visualiser.py, manual_run.py) to access paths through the new config structure. - Fixed bugs related to image processing and model saving. - Enhanced test infrastructure to accommodate the new configuration approach. This refactor improves code maintainability and clarity by centralizing configuration management.
2.5 KiB
2.5 KiB
Phase 6: Test Synchronization
Role: QA engineer and developer Goal: Reconcile the test suite with the refactored codebase — remove obsolete tests, update broken tests, add tests for new code Constraints: All tests must pass at the end of this phase. Do not change production code here — only tests.
6a. Identify Obsolete Tests
- Compare the pre-refactoring codebase structure (from Phase 0 inventory) with the current state
- Find tests that reference removed functions, classes, modules, or endpoints
- Find tests that duplicate coverage due to merged/consolidated code
- Decide per test: delete (functionality removed) or merge (duplicates)
Write REFACTOR_DIR/test_sync/obsolete_tests.md:
- Test file, test name, reason (target removed / target merged / duplicate coverage), action taken (deleted / merged into)
6b. Update Existing Tests
- Run the full test suite — collect failures and errors
- For each failing test, determine the cause:
- Renamed/moved function or module → update import paths and references
- Changed function signature → update call sites and assertions
- Changed behavior (intentional per refactoring plan) → update expected values
- Changed data structures → update fixtures and assertions
- Fix each test, re-run to confirm it passes
Write REFACTOR_DIR/test_sync/updated_tests.md:
- Test file, test name, change type (import path / signature / assertion / fixture), description of update
6c. Add New Tests
- Identify new code introduced during Phases 4–5 that lacks test coverage:
- New public functions, classes, or modules
- New interfaces or abstractions introduced during decoupling
- New error handling paths
- Write tests following the same patterns and conventions as the existing test suite
- Ensure coverage targets from Phase 3 are maintained or improved
Write REFACTOR_DIR/test_sync/new_tests.md:
- Test file, test name, target function/module, coverage type (unit / integration / blackbox)
Self-verification:
- All obsolete tests removed or merged
- All pre-existing tests pass after updates
- New code from Phases 4–5 has test coverage
- Overall coverage meets or exceeds Phase 3 baseline (75% overall, 90% critical paths)
- No tests reference removed or renamed code
Save action: Write test_sync artifacts; implemented tests go into the project's test folder
GATE (BLOCKING): ALL tests must pass before proceeding to Phase 7. If tests fail, fix the tests or ask user for guidance.