testing proposal: embed mozmill/jsbridge/mozrunner into mail/
asutherland at asutherland.org
Wed Mar 24 17:45:27 UTC 2010
MozMill seems to be making a habit of non-backwards-compatible
changes. Last time we upgraded it required some coordination, as all
There's another change along these lines that has landed:
It's basically a global search and replace of "plugins" with "addons".
While this seems like a reasonable nomenclature change and a likewise
reasonable decision not to complicate the code, it suggests that we are
using mozmill wrong by treating it as something to be installed
separately rather than something to be embedded*. (Note: We are not
using 'plugins' in-tree right now, but I am working on a patch so that
extensions can run mozmill tests via our framework, and it does care. I
am able to do something ugly to cover both cases, but it's ugly.)
For example, the Jetpack SDK has embedded mozrunner and jsbridge in its
This could also let us make meaningful enhancements to MozMill proper
without having to always hack around its limitations because otherwise
we need to depend on release cycles that can never happen fast enough.
(So, quasi-ironically, embedding would make us better open source
participants because sending things upstream becomes feasible.)
* Another option might be to require a specific version using
pkg_resources or what not. The downside to this is we need to wait for
the mozmill release cycle if we fix bugs/enhance mozmill in mozmill proper.
More information about the tb-planning