canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
(→MozMill and Leak & bloat tests.: Update based on current expectations.) |
|||
| Line 37: | Line 37: | ||
** This step currently blocked by {{bug|500201}} - MozMill is leaking lots of items. Hence moved to end. | ** This step currently blocked by {{bug|500201}} - MozMill is leaking lots of items. Hence moved to end. | ||
** Once we've got that support, I'd like to replace the existing Leak and Bloat tests (which currently use js files installed in chrome) with a mozmill version. This will help with the extensibility of the tests and give us a better base for which we can start extend those tests {{Bug|458351}}. | ** Once we've got that support, I'd like to replace the existing Leak and Bloat tests (which currently use js files installed in chrome) with a mozmill version. This will help with the extensibility of the tests and give us a better base for which we can start extend those tests {{Bug|458351}}. | ||
Suggestions: | |||
* A pass count of zero should return failure. | |||
* It would be neat if we could return the test results via a JSON blob | |||
somewhere rather than the current tradition of text-mangling. I am mainly | |||
thinking in terms of having a web UI that is better able to tell us where | |||
things went wrong. But that's just pipe-dreams and tinderpushlog with its | |||
magic already gets us more than 80% of the way towards usability... | |||