regression-consistency-checker

Run your test suite using pytest against two repository versions to detect regressions by analyzing differences in test passes, output values, exceptions, and performance metrics. This automated comparison identifies unintended behavior changes introduced by refactoring or library updates.

Yes, you can use pytest to verify behavior preservation after refactoring by running the regression checker. It compares test outcomes against a previous version to ensure bug fixes or new features do not break existing functionality or introduce unintended behavior changes.

Code version comparison identifies critical, high, medium, and low severity regressions in test passes, outputs, exceptions, and performance metrics. This severity classification helps prioritize which unintended behavior changes require immediate attention before deploying new code versions.

Yes, the regression checker uses difflib alongside pytest to compare test execution results between repository versions. This combination enables detailed analysis of output differences and exception changes, ensuring comprehensive regression detection across your test suite.

Automate regression testing for library updates by running your entire test suite against both old and new versions using the regression consistency checker. This confirms no existing tests fail and critical functionality remains intact, safeguarding backward compatibility.

You need regression testing after updating a library when you want to confirm that no existing tests fail and critical functionality remains intact. Compare test outcomes between old and new versions to detect severity-ranked regressions in outputs, exceptions, and performance.