Skip to content

Conversation

@jpinkney-aws
Copy link
Contributor

Problem

Features that depend on global state can cause test failures locally because the tests will use your current global state settings instead of a fake state for integ/e2e tests

Solution

integ/e2e tests should use a fake global state instead that automatically gets reset after each test


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jpinkney-aws jpinkney-aws requested a review from a team as a code owner February 12, 2025 19:07
@jpinkney-aws jpinkney-aws marked this pull request as draft February 12, 2025 19:07
@jpinkney-aws
Copy link
Contributor Author

/runIntegrationTests

1 similar comment
@jpinkney-aws
Copy link
Contributor Author

/runIntegrationTests

@jpinkney-aws
Copy link
Contributor Author

/runIntegrationTests

1 similar comment
@jpinkney-aws
Copy link
Contributor Author

/runIntegrationTests

@jpinkney-aws jpinkney-aws marked this pull request as ready for review February 13, 2025 18:28
Copy link
Contributor

@justinmk3 justinmk3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may want to start thinking about a base-class for test/globalSetup.ts and testInteg/globalSetup.ts. Seems like there is a lot of overlap.

@jpinkney-aws jpinkney-aws merged commit cd85e10 into aws:master Feb 13, 2025
28 of 32 checks passed
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
## Problem
Features that depend on global state can cause test failures locally
because the tests will use your current global state settings instead of
a fake state for integ/e2e tests

## Solution
integ/e2e tests should use a fake global state instead that
automatically gets reset after each test

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants