Thanks for this Blake. Somewhat related: for those of you using ESLint, I recently filed a bug to create a new custom ESLint rule that should help automatically detect CPOW usage in tests: https://bugzilla.mozilla.org/show_bug.cgi?id=1218412
On Thu, Oct 29, 2015 at 12:44 AM, Blake Kaplan <mrb...@mozilla.com> wrote: > Hello everybody, > > You might have heard that we're working on getting our testing situation > in line for e10s. To help people get started, I'm compiling a list of tips > that are useful to know when working on e10s tests (and e10s in general). > You can find it at <https://wiki.mozilla.org/Electrolysis/e10s_test_tips>. > > There isn't a catch-all solution to use to fix these tests, but there are > a few things to look out for. The key is to find places in tests where > objects from both chrome (like browser DOM nodes or chrome windows, etc.) > and content (docshells, content windows, etc.) are needed and to use > SpecialPowers or ContentTask to remote that bit to the other process. > > If a test is disabled because of a bug in e10s, please ensure that a bug > is on file and the e10s team has triaged it. > > I'm happy to answer questions as needed. > -- > Blake > > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
