Problem
VerificationEngine.verify stops after the first failing check and records remaining checks in skipped_checks. That is good for latency but hides stacked problems (e.g. syntax passes, imports fail, and you never learn test status until imports are fixed).
Impact
Slower debugging for authors and support; harder to prioritize multiple fix categories in one run.
Suggested direction
- Add a flag on the engine (e.g.
short_circuit: bool = True) or a CLI option on refactron verify (e.g. --all-checks) to run the full pipeline and aggregate failures.
- Clearly distinguish
passed, failed, and skipped in the result when short_circuit=False.
References
refactron/verification/engine.py (short-circuit loop)
Problem
VerificationEngine.verifystops after the first failing check and records remaining checks inskipped_checks. That is good for latency but hides stacked problems (e.g. syntax passes, imports fail, and you never learn test status until imports are fixed).Impact
Slower debugging for authors and support; harder to prioritize multiple fix categories in one run.
Suggested direction
short_circuit: bool = True) or a CLI option onrefactron verify(e.g.--all-checks) to run the full pipeline and aggregate failures.passed,failed, andskippedin the result whenshort_circuit=False.References
refactron/verification/engine.py(short-circuit loop)