Skip to content
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

[wptrunner] Support testdriver.js in {ref,print-ref,crash}tests #48486

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

jonathan-j-lee
Copy link
Contributor

WIP implementation for #13183 (will also need RFC)

This no-op refactor will allow other WebDriver executors, not just the
testharness executor, to perform testdriver actions.
This will allow non-testharness tests to use `testdriver.js` without
needing extra scripts. Evaluating `message-queue.js` is idempotent so
that, when using testharness with testdriver, the second inclusion is a
no-op.

Because resource scripts are cached, the size increase should not
meaningfully affect test performance.
@jonathan-j-lee jonathan-j-lee force-pushed the wptrunner/testdriver-reftest branch 2 times, most recently from f3e9cfb to 7568d4c Compare October 5, 2024 05:32
This will let wptrunner gracefully skip testdriver tests if the executor
doesn't support them.
@jonathan-j-lee jonathan-j-lee force-pushed the wptrunner/testdriver-reftest branch 3 times, most recently from 41b2fb1 to c4a6d69 Compare October 5, 2024 07:25
@jonathan-j-lee jonathan-j-lee reopened this Oct 5, 2024
@jonathan-j-lee jonathan-j-lee reopened this Oct 5, 2024
@jonathan-j-lee jonathan-j-lee force-pushed the wptrunner/testdriver-reftest branch 2 times, most recently from 3796049 to 7b80717 Compare October 7, 2024 17:14
Non-testharness executors that don't support testdriver simply skip
those tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant