E2E - Enhance Mandatory MFA scenarios if the token is invalid #389
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
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.
Motivation and Context
Test is not stable sometimes because of the invalid token
Work around to re-input the token
Jira Link:
https://toruslabs.atlassian.net/browse/PD-3787
https://github.com/Web3Auth/web3auth-e2e-tests/actions/runs/10463993434
Description
Increase the timeout to 120s
Handle to re-input the token
How has this been tested?
Run locally
Check by Github action
Screenshots (if appropriate):
Types of changes
Enhance script
Checklist: