behavior-preservation-checker

To check for behavioral regressions after a code migration, compare test outcomes, execution traces, and observable outputs between the original and migrated codebases to detect semantic changes and ensure behavioral equivalence.

Behavioral equivalence testing during refactoring is the process of analyzing runtime behavior and observable outputs between original and updated code repositories to verify that code transformations do not introduce unintended semantic changes or regressions.

Yes, you need pytest to run the automated behavior comparison scripts. The Skill requires pytest as a dependency to execute tests and analyze test outcomes when comparing original and migrated code repositories.

The best way to verify Python 2 to Python 3 migration behavior is to automatically compare test results and execution traces between the original and migrated repositories to confirm that all existing tests still pass and runtime behavior remains identical.

Migrated code fails tests that previously passed due to behavioral deviations introduced during the code transformation. The Skill identifies these specific regressions by comparing test outcomes between the original and migrated codebases and provides actionable guidance for fixing them.

Yes, you can save a code comparison report to a specific file path. The Skill allows you to compare original and migrated repositories and save the detailed behavioral comparison output directly to a JSON file.