Confirmed users
656
edits
Auto-tools/Projects/Mochitest on Mozbase: Difference between revisions
Jump to navigation
Jump to search
Auto-tools/Projects/Mochitest on Mozbase (view source)
Revision as of 19:05, 7 May 2013
, 7 May 2013no edit summary
No edit summary |
|||
| Line 11: | Line 11: | ||
=== Milestone 1 - 2 weeks (started: April 8) === | === Milestone 1 - 2 weeks (started: April 8) === | ||
* [ahal] {{miss|Use mozprocess}}/devicemanager for process management, instead of automation.py.in, for B2G mochitest. | |||
* [ahal] {{done|Decide}} on a method of solving the package update problem ({{bug|855893}}). | |||
* [jhammel] {{miss|Get}} mozbase tests running during 'make check' ({{bug|790765}}). | |||
=== Milestone 2 - 2 weeks (tentative start: April 29) === | |||
* [ahal] Use mozprocess/devicemanager for process management, instead of automation.py.in, for B2G mochitest. | * [ahal] Use mozprocess/devicemanager for process management, instead of automation.py.in, for B2G mochitest. | ||
* [jhammel] Get mozbase tests running during 'make check' ({{bug|790765}}). | * [jhammel] Get mozbase tests running during 'make check' ({{bug|790765}}). | ||
=== Milestone | === Milestone 3 - 2 weeks (planned) === | ||
* Implement method selected to solve package update problem ({{bug|855893}}) - currently, move away from puppetagain; use in-tree mozbase for in-tree tests. | * Implement method selected to solve package update problem ({{bug|855893}}) - currently, move away from puppetagain; use in-tree mozbase for in-tree tests. | ||
* Use mozprocess/mozrunner for process management in desktop mochitest, instead of automation.py.in. | * Use mozprocess/mozrunner for process management in desktop mochitest, instead of automation.py.in. | ||