[wpt-sync] Sync PR 60672 - Enable WebExtension tests support in wptrunner for Chrome.
Categories
(Testing :: web-platform-tests, task, P4)
Tracking
(firefox154 fixed)
| Tracking | Status | |
|---|---|---|
| firefox154 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 60672 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/60672
Details from upstream follow.
justinlulejian <justinlulejian@users.noreply.github.com> wrote:
Enable WebExtension tests support in wptrunner for Chrome.
Before this change, wptrunner did not support running WebExtension tests for Chrome. It didn't have the ability to detect extension tests and apply necessary Chrome flags (like enabling the extension test API on webpages).
Additionally, the WebDriver BiDi extension installation/uninstallation implementation in wptrunner was incorrect.
self.webdriverrefers to theSessionobject instead of theWebDriverBidiProtocolobject, which contains theloop()method. Alsoinstall()anduninstall()methods expect keyword arguments, not positional arguments.After this change, wptrunner should be able to run WebExtension tests. It detects them based on path and applies Chrome flags that enable the
(chrome|browser).testJS API. The WebDriver BiDi implementation is also updated to use the expected keyword parameters andWebDriverBidiProtocolloop.Context: crbug.com/493946943
| Assignee | ||
Comment 1•2 months ago
|
||
| Assignee | ||
Comment 2•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
| Assignee | ||
Comment 3•2 months ago
|
||
| Assignee | ||
Comment 4•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
| Assignee | ||
Comment 5•2 months ago
|
||
| Assignee | ||
Comment 6•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
| Assignee | ||
Comment 7•2 months ago
|
||
| Assignee | ||
Comment 8•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
| Assignee | ||
Comment 9•2 months ago
|
||
| Assignee | ||
Comment 10•2 months ago
|
||
| Assignee | ||
Comment 11•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
| Assignee | ||
Comment 12•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Comment 13•2 months ago
|
||
| Assignee | ||
Comment 14•2 months ago
|
||
Test result changes from PR not available.
Comment 15•2 months ago
|
||
| bugherder | ||
Description
•