[馃悰 Bug]: browser runner - alert or confirm stales execution of runner
#10048
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
christian-bromann
added
Bug 馃悰
help wanted
christian-bromann
added
PR: Polish 馃拝
christian-bromann
force-pushed
the
cb-popup-spy
branch
from
f774599
to
97f2399
Compare
christian-bromann
force-pushed
the
cb-popup-spy
branch
from
97f2399
to
17331a0
Compare
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.
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
latest
Node.js Version
latest
Mode
WDIO Testrunner
Which capabilities are you using?
anyWhat happened?
When an
alertorconfirmis triggered in the browser, all execution comes to an halt. This causes also the test to stop and it is impossible for the user to resume without manually interacting with the browserWhat is your expected behavior?
Have these methods mocked automatically to avoid this edge case.
How to reproduce the bug.
n/a
Relevant log output
Code of Conduct
Is there an existing issue for this?