-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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] Decouple testdriver infrastructure from testharness #49044
[wptrunner] Decouple testdriver infrastructure from testharness #49044
Conversation
fcfd0c8
to
0f2c1f4
Compare
8e59e23
to
8469799
Compare
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.
8469799
to
a2ce584
Compare
@KyleJu @DanielRyanSmith Force merge due to unrelated failure #49545? If possible, please use the rebase method, not squash, since each commit works standalone. The changes in this PR are primarily covered by the |
Split off from #48486 in preparation for #13183. This PR itself should be a no-op, so it need not block on web-platform-tests/rfcs#211.