Repository navigation
Use backend URLs for VuMark and rate-limit tests - #3754
Merged
Merged
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The shared VuMark suite and target-list rate-limit test still use the production VWS URL. Pass
base_vws_urlthrough both VuMark helpers and every caller, configure the locally created VWS client with it, and use the fixture in the rate-limit request.This lets the existing SDK and raw-request assertions run against a service address supplied by another repository. Part of #3738 and #3737. It is independent of the unmatched-request adapter work in #3753.
Validation:
git diff --checkpasses.This changes five test files, with no source package, dependency, workflow, or coverage gate changes. Hosted full-suite validation will run on this PR.