Skip to content
This repository was archived by the owner on Oct 30, 2026. It is now read-only.

Separate Flask backend setup from test selection - #3820

Merged
adamtheturtle merged 2 commits into
mainfrom
codex/separate-flask-backend-setup-20261029
Oct 29, 2026
Merged

adamtheturtle merged 2 commits into
mainfrom
codex/separate-flask-backend-setup-20261029

Conversation

@adamtheturtle

@adamtheturtle adamtheturtle commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Towards #3738 and #3741.

Move Flask registration, Model Target setup, unmatched-request transport and target-manager control operations out of the fixture-selection plugin into flask_backend.py. Import the server applications directly from vws_mock_server. Share VuMark database construction with the in-memory adapter through a small mock_databases.py helper.

The existing plugin keeps fixture names, backend identities, parametrization and skip policy. This separates concrete Flask operations so they can move with the server adapter later.

Validation:

  • AST audit confirms preserved definitions apart from delegated names and a location-independent docstring; the database-creation HTTP branch is unchanged.
  • Existing focused contract and credential tests: 503 passed, 243 skipped (real backend excluded).
  • Isolated installed-wheel consumer passes.
  • All pre-commit and pre-push hooks, partition checks and type checkers pass; changed-file Pylint reports 10/10.

No new test assertions or retry behavior are introduced.

This branch was successfully deployed

1 active and 1 inactive deployments
vuforia — eb7b24f0 Deployed Oct 29, 2026 by adamtheturtle via ci-tests (3.15, docs/) #2707
development — eb7b24f0 Deployed Oct 29, 2026 by adamtheturtle via pages #2577
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant