This repository was archived by the owner on Oct 30, 2026. It is now read-only.
Repository navigation
Separate Flask backend setup from test selection - #3820
Merged
Merged
Conversation
adamtheturtle
had a problem deploying
to
vuforia
October 29, 2026 10:39 — with
GitHub Actions
Failure
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 fromvws_mock_server. Share VuMark database construction with the in-memory adapter through a smallmock_databases.pyhelper.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:
No new test assertions or retry behavior are introduced.