Conversation
Tests should ideally be isolated from the user's environment.
1 task
|
Closing & backlogging work: #4749 |
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
2 participants
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.
A user who runs this repository's test suite could also reasonably have variables like
BROWSERorGLAMOUR_STYLEset in their environment. Some of our tests fail because those outside environment variables bleed into tests.This change introduces a helper to safely stub environment variable values with, as well as configures out test suite in CI to run in an environment with a bunch of values that could possibly affect gh runtime, but shouldn't do so for tests.