Fix ResourceDetailsTests flaky failures when switching resources #12847
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.
Description
Fixes #12101
Two tests were switching from resource "app1" to resource "app2" but only updating the
Resourceparameter, leavingResourceByNamecontaining the old resource. This created an inconsistent state that could trigger dictionary key collisions in internal component tracking, manifesting as "An item with the same key has already been added" errors.Changed:
ClickMaskAllSwitch_NewResource_MaskChanged: Now updatesResourceByNamewhen switching to resource2ClickMaskEnvVarSwitch_NewResource_MaskChanged: Now updatesResourceByNamewhen switching to resource2Both tests now maintain parameter consistency by including the new resource in
ResourceByName:Checklist
<remarks />and<code />elements on your triple slash comments?doc-ideatemplatebreaking-changetemplatediagnostictemplateOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.