Auto-tools/Projects/MozBase/Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Course of Action: add moztest)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Mozbase on Mozilla Central ==
#REDIRECT [[Auto-tools/Projects/Mozbase/Roadmap]]
 
The test harnesses on mozilla-central should make use of mozbase:
https://wiki.mozilla.org/Auto-tools/Projects/MozBase
 
This text is a road map for the initial phase of getting testing on
mozilla-central to make use of mozbase.  More issues will come up in
tackling this initial workload which should be tracked: both in terms
of m-c integration and in mozbase bugs and enhancements. Likewise,
once these problems are solved vistas will be open to make testing
better that will extend the roadmap.
 
 
=== Building blocks ===
 
A lot of work has already been done to make this possible
 
* virtualenv in $OBJDIR {{bug|661908}}
 
 
=== Course of Action ===
 
See {{bug|775756}} for the tracking bug
 
* [http://mxr.mozilla.org/mozilla-central/source/build/automation.py.in automation.py.in]
** remove interpolation of this file: {{bug|688665}}, {{bug|746546}}
*** This is harder than it looks; see {{bug|683397}}
** convert this file to mozbase: {{bug|688667}}
 
* port profileserver to mozbase: {{bug|746244}}
 
* remove duplicate code from m-c: {{bug|707976}}
** two copies of manifest destiny
*** remove duplicate
*** use the version installed in the virtualenv
*** remove manifest destiny tests: http://mxr.mozilla.org/mozilla-central/source/build/tests/
** two copies of mozinfo
*** remove duplicate
*** use the version installed in the virtualenv
** devicemanager in http://mxr.mozilla.org/mozilla-central/source/build/mobile/ should be moved to use testing/mozbase/devicemanager
 
* move some subset of our python to a top level directory {{bug|775243}}
 
* move everything that rolls its own json de/serializer to use simplejson: {{bug|769849}}
** we need to figure out *all* the places that we do this and fix them
 
* port TPS to modern mozbase: {{bug|771554}}
 
* port automationutils.py to mozbase: http://mxr.mozilla.org/mozilla-central/source/build/automationutils.py
 
* implement MozTest for test results: {{bug|774419}}
 
* port mochitest to mozbase: {{bug|746243}}
 
* port reftest to mozbase: {{bug|746246}}
 
* port xpcshell to mozbase: {{bug|771578}}
 
* get rid of pythonpath.py: {{bug|774911}}
** http://mxr.mozilla.org/mozilla-central/source/config/pythonpath.py
** http://mxr.mozilla.org/mozilla-central/source/js/src/config/pythonpath.py
 
* moztest: {{bug|774419}}
 
=== Other considerations ===
 
We should have an automated way of mirroring between m-c and github:
https://bugzilla.mozilla.org/show_bug.cgi?id=722451 Not a blocker to
any of the above strictly but something to keep in mind
 
== Roadmap Next ==
 
There are several exciting things we can do once the harnesses are on mozbase:
 
* adding manifestparser to mochitest: {{bug|563724}}
* add the ability to output failed (or whatever) results to a manifest so that they can be tried again

Latest revision as of 21:55, 22 January 2013