Skip to content

Separate report timing coverage from the shared suite - #3757

Merged
adamtheturtle merged 1 commit into
mainfrom
separate-report-timing-test-20261013
Oct 13, 2026
Merged

adamtheturtle merged 1 commit into
mainfrom
separate-report-timing-test-20261013

Conversation

@adamtheturtle

Copy link
Copy Markdown
Member

The shared recognition-count report directory includes a processing-delay test that constructs its own MockVWS instance. Move that test into the core Requests test area so the shared suite can be collected without importing the in-memory implementation.

The function body, parameterization, and Beartype configuration are preserved. Its integer, float, and fractional delay cases now each run once. Previously the directory's outer backend fixture ran each case twice, even though both executions used the test's own in-memory mock. The remaining 52 shared report cases continue to run across both mock adapters.

Part of #3738 and #3737. Independent of #3756. The new module is covered by the existing Requests directory CI partition, so no workflow change is needed.

Validation:

  • AST comparison confirms that every original function body and decorator is preserved, including all three timing parameters.
  • Python 3.15: all 55 report cases pass with synthetic credentials and retries disabled: 52 shared cases and three core timing cases.
  • A separate consumer loads the same shared test functions and existing adapters at custom loopback HTTP URLs: all 52 shared cases pass.
  • The complete shared report directory and new core test module have 100% local statement and branch coverage.
  • Pre-commit and pre-push checks pass, including CI partition validation, Mypy, Pyright, public type completeness, Ty, Pyrefly, and check-manifest. Pylint passes on both changed files, and git diff --check passes.

Only two test files change. Source code, workflows, dependencies, real-service restrictions, and coverage gates are preserved. Hosted full-suite verification will run on this PR.

This branch was successfully deployed

2 active deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant