reclassify-tests

You can separate core spec tests from inferred functionality tests by analyzing checkpoint spec examples against your test files and marking non-explicit behaviors with @pytest.mark.functionality. This clarifies which tests demonstrate core requirements versus extended coverage.

Test reclassification by spec coverage is the process of identifying tests whose behavior is not explicitly demonstrated in the checkpoint spec and tagging them as functionality. It distinguishes core demonstration from inferred behavior to clarify test suite scope.

To mark implicit test behaviors as functionality using pytest marks, analyze your spec examples and test files to find behaviors not explicitly shown, then apply @pytest.mark.functionality to those tests and generate a reclassification report detailing the decisions.

Yes, you can analyze pytest fixtures alongside spec examples and test files to determine core versus functionality coverage across checkpoints. The analysis identifies which tests demonstrate explicit spec behavior and which test inferred functionality.

Some pytest tests are not explicitly demonstrated in the checkpoint spec because they verify inferred or extended behaviors beyond the core examples. Reclassification identifies these tests and marks them as functionality to separate core demonstrations from implicit coverage.

Test reclassification both generates a reclassification report detailing decisions and rationale, and outputs any test modifications needed for review. This includes applying pytest marks to classify tests based on spec coverage analysis.