Closed Bug 1555701 Opened 5 years ago Closed 5 years ago

Set up test job for WPT WebDriver tests with Fission enabled

Categories

(Testing :: geckodriver, task, P3)

Version 3
task

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ato, Unassigned)

References

Details

In order to figure out how much Marionette is affected by Fission,
we ought to have a (tier 3?) job of the WebDriver Web Platform Tests
(Wd) running with it enabled. There is precedence for this with
other test jobs.

Priority: -- → P3

jwatt, what exactly are the right preferences to set?

Flags: needinfo?(jwatt)
Component: Marionette → geckodriver
See Also: → 1555704

See also https://bugzilla.mozilla.org/show_bug.cgi?id=1555704 about
writing some cross-origin <iframe> WebDriver tests for WPT.

Hm, I'm sure that I have seen some wdspec tests running for fission in CI but I cannot remember where that was. I just tried to check but whether on m-c, nor autoland or try those jobs are visible. :/

So the fission jobs can actually be triggered via try, and the wdspec results look good:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=b0054681c542c7f21e571aafb674f4e82f536b96&selectedJob=251597178

I don't think that we will further need this bug, given that once fission is ready for testing, all the jobs will be running on trunk by default.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(jwatt)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.