Closed Bug 1964755 Opened 10 days ago Closed 8 days ago

Make it easier to run mochitest-browser tests on try with updated system add-on XPIs

Categories

(Testing :: Mochitest, task)

task

Tracking

(firefox140 fixed)

RESOLVED FIXED
140 Branch
Tracking Status
firefox140 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

(Blocks 1 open bug)

Details

(Whiteboard: [hnt-trainhop])

Attachments

(1 file)

It looks like if we push a change to try such that the build will result in an XPI being placed under objdir/_tests/testing/mochitest/extensions, that the mochitest test runner will take care of having that extension be installed before running any of the tests.

It doesn't look like, however, we have anything placing extensions there. What I'd like to do is add a moz.build rule that'll allow developers to use try pushes with an XPI placed within testing/mochitest/extensions, and that when building, those will get placed within objdir/_tests/testing/mochitest/extensions.

I have a try push here which demonstrates the technique: https://treeherder.mozilla.org/jobs?repo=try&revision=60ede86ab25f53aa197576755874d77851dfe91e

Not only is it installing the newtab XPI (the XPI dumps "Starting up newtab version 140.0.0" to the console, which can be seen in the test logs), but the push also includes updated newtab mochitest-browser tests grafted in from the main repository.

PIs can then be placed within testing/mochitest/extensions, and
these will automatically be installed and enabled when running
the mochitests on try.

Pushed by mconley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cd7deb6b7722 Make it easier to install an addon during mochitest-browser tests on try pushes. r=jmaher
Status: NEW → RESOLVED
Closed: 8 days ago
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: