chore: set environment variable using extensions in tests #2798
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
JoeWang1127
commented
May 22, 2024
| private static final String DEFAULT_ENDPOINT = "test.googleapis.com:443"; | ||
| private static final String DEFAULT_MTLS_ENDPOINT = "test.mtls.googleapis.com:443"; | ||
| private EndpointContext.Builder defaultEndpointContextBuilder; | ||
| private StatusCode statusCode; | ||
|
|
||
| @SystemStub private final EnvironmentVariables environmentVariables = new EnvironmentVariables(); |
There was a problem hiding this comment.
Looks like there's no straightforward way to set environment variables in Junit 5.
I followed this post to use systemstubs.
The library is under MIT license and we're free to use. See go/licensetable.
|
|
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.
Fix: #2785