Summary
Run and especially Stop behavior are under-tested and rely heavily on slow integration paths.
Problem
Critical startup/shutdown error handling lacks deterministic unit coverage.
Scope
- Refactor minimally for dependency injection where needed
- Add table-driven unit tests for success/error paths in
Run and Stop
- Keep integration tests for full-stack behavior only
Acceptance Criteria
- Error and success paths in
Run and Stop are unit-tested
Stop shutdown behavior is verified deterministically
- Affected test suite runs without external services
References