run-tests

To detect regressions, run automated pytest suites targeting your full codebase or specific modules. This validates implementation correctness by executing tests and surfacing any failures, ensuring new changes do not break existing functionality.

You can run focused module tests by configuring pytest selection to target specific modules like roll, character, or core. This isolates issues efficiently during development by executing only the relevant tests for the area you are changing.

Yes, you can generate coverage reports by executing pytest with optional coverage flags. This tracks testing quality and produces a readable test report, helping prevent untested regressions in critical logic like dice rules or character sheets.

Yes, you need uv to sync dev dependencies before running automated test suites. This ensures your environment has all required packages installed, allowing pytest to execute properly for CI validation and regression detection.

Python 3.10 or higher is required to execute pytest test suites for module regression. This version prerequisite ensures compatibility with the test automation framework and the codebase dependencies needed for full validation.

Pytest test automation may fail during full validation if dev dependencies are not installed via uv sync, or if the environment lacks Python 3.10+. Surfaces failures and coverage gaps indicate implementation regressions that need fixing.