Auto-tools/Projects/Mochitest on Mozbase: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 6: Line 6:


=== Milestone 0 (completed 2013/03/29) ===
=== Milestone 0 (completed 2013/03/29) ===
* Replace profile manipulation in b2gautomation.py with mozprofile.
* {{done|Replace}} profile manipulation in b2gautomation.py with mozprofile. '''ahal'''
* Flesh out mozbase docs for mozhttpd, moznetwork, mozdevice.
* {{done|Flesh}} out mozbase docs for mozhttpd, moznetwork, mozdevice. '''wlach'''
* Use mozcrash for crash detection and reporting in all mochitest runners.
* {{done|Use mozcrash}} for crash detection and reporting in all mochitest runners. '''ted, ahal'''


=== Milestone 1 - 2 weeks (tentative start: April 8) ===
=== Milestone 1 - 2 weeks (tentative start: April 8) ===

Revision as of 19:22, 9 April 2013

Goal 2013 Q2

Move desktop and B2G mochitest atop mozbase

Approach and Milestones

  • TODO: Add bugzilla bug queries to this by attaching proper whiteboard flags to the relevant bugs that are filed.

Milestone 0 (completed 2013/03/29)

  • [DONE] Replace profile manipulation in b2gautomation.py with mozprofile. ahal
  • [DONE] Flesh out mozbase docs for mozhttpd, moznetwork, mozdevice. wlach
  • [DONE] Use mozcrash for crash detection and reporting in all mochitest runners. ted, ahal

Milestone 1 - 2 weeks (tentative start: April 8)

  • [ahal] Use mozprocess/devicemanager for process management, instead of automation.py.in, for B2G mochitest.
  • [ahal] Decide on a method of solving the package update problem (bug 855893).
  • [jhammel] Get mozbase tests running during 'make check' (bug 790765).

Milestone 2 - 2 weeks (tentative start: April 29)

  • Implement method selected to solve package update problem (bug 855893).
  • Use mozprofile for profile manipulation in desktop mochitest, instead of automation.py.

Milestone 3 - 2 weeks (planned)

  • Use mozprocess/mozrunner for process management in desktop mochitest, instead of automation.py.in.

Milestone 4 - 2 weeks (planned)

  • Use mozlog for logging in desktop mochitest.
  • Use moztest as a result container for mochitest. (?)

Future milestones

  • Develop a remote mozrunner API for running Firefox on remote devices.
  • Port fennec mochitest to mozbase.