-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Add tests for thenables returned from async script #57160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jugglinmike
wants to merge
6
commits into
master
Choose a base branch
from
webdriver-classic-async-promise-resolution
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+34
−0
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
160437b
Add tests for thenables returned from async script
jugglinmike 240ebfc
Incorporate review feedback
jugglinmike 1c51e92
Merge remote-tracking branch 'upstream/master' into webdriver-classic…
jugglinmike 192af48
Remove assertions for response data
jugglinmike b6904bc
Clarify test
jugglinmike c678159
Remove assertion for response data
jugglinmike File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we do it actually similar to the above case for fulfillment and resolve the promise with a different error? That way
Promise.rejectshould still have precedence, right?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, yes. I didn't recognize how renaming the test made the callback relevant here. I've made that change and pushed it to this branch.
Doing so helped me recognize that we're not being completely systematic here. There are three variables: the callback result (which should be considered an error if it is a rejected promise), the promise result, and the sequence in which they occur.
I think we actually need 8 tests, not just two:
test_callback_success_then_promise_successtest_promise_success_then_callback_successtest_callback_error_then_promise_successtest_promise_success_then_callback_errortest_callback_success_then_promise_errortest_promise_error_then_callback_successtest_callback_error_then_promise_errortest_callback_error_then_promise_errorThough, given that we can't differentiate between script errors, we might skip those final two tests.
What do you think?
Footnotes
We'll change these if-and-when https://github.com/w3c/webdriver/pull/1939 lands ↩ ↩2