Most of the debugger tests are currently enabled for e10s, but only for opt builds. The reason for this is bug 1073352, which causes most, if not all, the tests to leak in e10s debug builds. One bug 1073352 lands, the debugger tests need to be explicitly enabled for e10s debug builds, which is what this bug is about.

e10s test

This first patch enables 4 tests which were failing because they were using EventUtils to send mouse events to the content process. They have been migrated to use BrowserTestUtils. addTab in head.js as also been migrated to use BrowserTestUtils.browserLoaded. try : https://treeherder.mozilla.org/#/jobs?repo=try&revision=cfb47f7bec4f

I removed all the skips from browser.ini and pushed to try. This attachment contains the aggregated list of all the debugger tests that failed on e10s. (43 tests total). Missing information about Linux debug tests: e10s devtools tests are not enabled for such builds yet.

Ran local tests in e10s debug mode, with only 55 tests disabled (down from 218) and it was successful. (the disabled tests are more or less the ones that are in my previous attachment + some that kept failing with e10s + debug). Try push : https://treeherder.mozilla.org/#/jobs?repo=try&revision=2a12b42b200c

Bug 1103839 - Fix dbg tests calling script in content process Now using ContentTask.spawn instead of directly calling the child process page (see https://wiki.mozilla.org/Electrolysis/e10s_test_tips#ContentTask). Unskipped related tests in browser.ini We are down to 52 skipped tests total, with 46 related to e10s. Try https://treeherder.mozilla.org/#/jobs?repo=try&revision=3c2331e9bffb