On Tuesday, January 5, 2016 at 2:38:30 PM UTC-5, Felipe G wrote: > (cross-posted to fx-dev and dev.platform) > > As we drive towards shipping e10s, we are working on making sure that our > tests work with e10s. As you already know, there's a number of tests that > are disabled from running on e10s, and we need to enable them. We've > created a spreadsheet that lists every test that is disabled from running > on e10s in order to track the remaining work to do. ..
We've managed to enable a good number of tests in the last couple of weeks. Thanks to those who have looked at the disabled tests list and added comments or fixed tests: https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit?pref=2&pli=1#gid=0 Many tests still lack owners, or at least a mentor who could help someone else fix and/or enable the test. If a test shouldn't be enabled in e10s at all, please add a comment to the manifest file (such as mochitest.ini) indicating the reason. browser-plain: many of these are under dom/ browser-chrome: good progress here. Several browser/ components need owners and work. devtools tests: hundreds of tests here. The devtools team have assigned owners to these (thanks!) but I assume they will need lots of help. I expanded the documentation at https://wiki.mozilla.org/Electrolysis/e10s_test_tips for browser-chrome tests. These tips describe utility functions that can help for converting existing tests and for writing new tests. This is based on a similar talk I gave during the last work week. I can help anyone with converting and enabling tests; if not, the rest of the e10s team will be happy to help with any test issues. Neil _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
