ln-513-regression-checker

To auto-detect and run test suites for regressions, the checker identifies your framework (pytest, jest, vitest, or go test), builds the appropriate commands, and executes them with a 5-minute timeout to output a PASS/FAIL verdict. It captures stdout/stderr for audit trails.

The best way to run a non-intrusive quality gate without modifying ticket statuses is using a regression checker that executes your existing test suite and reports pass/fail counts with failing test details, ensuring no external statuses or tasks are altered during the process.

Yes, the regression checker supports JavaScript test framework detection for both jest and vitest. It automatically identifies the configured framework, runs the full suite, and parses the pass/fail counts to report key failures for quick triage.

To capture stdout and stderr logs when running pytest regression tests, the checker executes the suite and preserves both output streams automatically. This allows downstream log analysis and provides an audit trail alongside the PASS/FAIL verdict and failing test details.

If your test suite execution exceeds the 5-minute timeout during regression detection, the run is terminated. The checker applies this strict limit when building and executing test commands across pytest, jest, vitest, or go test frameworks to ensure quick quality gate feedback.

The regression checker reports a FAIL verdict without modifying project tickets because it functions as a non-intrusive quality gate. It solely runs the existing test suite, captures the results, and outputs the verdict with failing test details for manual triage.