I've been a little hesitant to plug this as it's a prototype and the UX is pretty terrible. Also the underlying database it's using is not super resilient. But people might find it useful for this effort and I don't have time to improve it much more anyway, so what the heck.
This is basically what came of those "Test Informant Reports" I was posting awhile back: http://people.mozilla.org/~ahalberstadt/test-informant/ If you don't care about seeing how many tests were added or removed over a period of time, set both the start and end dates to the same day. Known issues: 1. Doesn't work over https (add an exception to https everywhere) 2. Setting either of the dates to a weekend or the current day may cause weird results. This is because it's using data on the actual jobs that got run that day. E.g if you set the end date to a Sunday and it so happens that no PGO jobs were run, it'll interpret that as all PGO tests getting disabled. It's a static client-side script, not an intelligent web service. 3. Querying can be slooowww. Limit the number of suites. -Andrew p.s I'm terrible at webdev. Also I don't really have time for this. If anyone is interested in improving/taking this over, let me know. Source is here: https://github.com/mozilla/test-informant On 05/01/16 02:38 PM, 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. https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit?usp=sharing Please take a look at the list and help in any way you can. Feel free to add your name to any test that you pick to fix, or add comments about tests that you have knowledge about. Even a comment describing what the test is testing and/or what it takes to make it pass on e10s helps. For tests that can't be fixed in the timeframe of shipping e10s, we will consider manual testing of the things that they are supposed to test. But of course that's a stop gap solution until they can be properly fixed. Blake and I will be reaching out to module owners and peers to find owners for tests. It is each team's responsibility to ensure that their features are properly tested under e10s! So do help and spread the word around. There's a wiki page with tips on how to convert tests: https://wiki.mozilla.org/Electrolysis/e10s_test_tips, and Blake has also written about it recently: https://blog.mozilla.org/mrbkap/2015/12/10/converting-a-test-to-be-e10s-compatible/ . Ping me, mrbkap or anyone in #e10s if you have questions! Felipe
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
