canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
(Initial version) |
(→MozMill and Leak & bloat tests.: Update based on current expectations.) |
||
| Line 25: | Line 25: | ||
The rough plan is this: | The rough plan is this: | ||
# {{Bug|458352}} | # <strike>{{Bug|458352}} support for different profiles when running tests</strike> | ||
# {{Bug|500142}} Integrate mozmill into the build system - tests can be run with "make mozmill" and "make mozmill-one" | |||
# {{Bug|504304}} Test VM/buildbot slave for initial results and automation. Aim is to a) check the stability, b) use as a platform for implementing and testing the necessary mozmill test support infrastructure, c) get initial results alongside builds on day-to-day basis. | |||
# {{Bug|500142}} | # Bug TBD. Once support infrastructure is stable, expand mozmill tests across platforms. | ||
# Once package-tests | |||
Future: | |||
* Bug TBD Hooking Mozmill up to make package-tests. | |||
** This would allow non-devs to download a test package and run alongside builds. Could also move mozmill tests to a separate slave if required. | |||
* {{Bug|458352}} Hooking Mozmill up to Leak and Bloat tests. | |||
** 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}}. | |||