test(qa): follow canonical frontier defaults#104722
Merged
Merged
Conversation
Contributor
Author
|
Merged via squash.
|
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
1 participant
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.
What Problem This Solves
The July release branch correctly defaults QA Lab's live-frontier lane to GPT-5.6, but four downstream tests still hard-code GPT-5.5. Plugin Prerelease therefore fails deterministically even though the runtime and canonical model-selection tests agree on GPT-5.6.
Why This Change Was Made
Backport the canonical QA test fix from
main: derive default and fallback expectations throughdefaultQaProviderModelForMode("live-frontier")while preserving explicit GPT-5.5 override coverage and the mocked idle-snapshot assertion.User Impact
No runtime behavior changes. July release validation now tests the canonical live-frontier default instead of a stale literal.
Evidence