E2E tests: keep token in memory instead of writing to file #1018
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
andreasphil
force-pushed
the
flaky-e2e
branch
2 times, most recently
from
130fa26 to
9d0da67
Compare
andreasphil
force-pushed
the
flaky-e2e
branch
from
9d0da67 to
fcfb2f7
Compare
This is mostly to simplify E2E testing. Since the E2E tests can sometimes take more than 5 minutes (the default token lifespan), it could happen that the token used by the E2E tests expires during long-running tests. Refreshing the token for the E2E tests is a bit complicated, so for now we'll just extend the token lifespan of the local Keycloak to avoid the issue. RISDEV-0000
|
|
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.
Writing the token to a file causes flaky tests, and it might not actually be necessary.
RISDEV-0000