Repository navigation
Declare backend capabilities for the shared API tests - #3758
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.
Shared ordering, Content-Length, and rate-limit tests still choose behavior by concrete backend identity. Replace all six remaining backend-name conditions in shared assertions with a typed
BackendCapabilitiesfixture.The adapter declares deterministic target/duplicate order, deterministic query order, prompt oversized-body responses, and a rolling rate-limit window. Native defaults preserve the existing behavior: both mocks enable all four; real Vuforia enables none. Consumers can override each capability independently. Skip messages describe unsupported behavior, and the original request/assertion bodies are preserved.
Part of #3738 and #3737. After this change, comparisons against concrete backend enum members are confined to the adapter module.
Validation:
git diff --checkpasses.Source package behavior, workflows, dependencies, real-service restrictions, and coverage gates are preserved. Hosted full-suite validation will run on this PR.