test(amazonq): reset global state before each test #6661
+73
−17
Conversation
This file contains 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
|
/runIntegrationTests |
1 similar comment
|
/runIntegrationTests |
jpinkney-aws
force-pushed
the
clear-global-staets
branch
6 times, most recently
from
d42f821 to
0fe5ff7
Compare
jpinkney-aws
force-pushed
the
clear-global-staets
branch
from
565cf5f to
6d53ccb
Compare
jpinkney-aws
force-pushed
the
clear-global-staets
branch
from
6d53ccb to
450d1a5
Compare
justinmk3
approved these changes
Feb 25, 2025
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.
Problem
previously we avoided resetting the global states because it didn't have it stubbed for integ/e2e tests
Solution
Now that it is we can allow global state to reset in the inline tests
feature/xbranches will not be squash-merged at release time.