On Fri, May 15, 2015, at 02:26 PM, Henrik Skupin wrote: > Yes, its a very outdated version of Mozmill from the hotfix-1.5 branch, > which we do not support since more than a year. Given that I have to add > that we cannot maintain something which is not in use at all. It's sad > to say but if something is broken the TB devs will have to get it fixed > in their customized Mozmill version.
This shouldn't be too big a problem. The Thunderbird mozmill tests basically do the following: - Spin up a Thunderbird instance with a controlled profile with the mozmill extension in place that provides various testing code, and listens so python can connect and tell jsbridge to do things. - Use jsbridge to launch JS testing logic in-process that synchronously (using nested event loops) pokes things and waits for things, with a layer of helper functions wrapping the lower level mozmill functionality. - Detect crashes maybe, consume the results. I would expect most of the brittleness to be related to: - changes in how Gecko/Toolkit decides to use (or not use) extensions as things are locked down to stop bad-actor-sneakily-installed extensions - minor moz-specific DOM API changes that mozmill's helper logic depended on - Keeping up with Python 2.x releases? It certainly doesn't seem worth it / feasible to convert to the Gaia/JSMarionette style of operation where synchronous JS code is run in a node.js process and remotes all checks. At least not at this time. If/when Thunderbird ever goes more e10s, that would likely be the time to overhaul the tests. Many of which could hopefully be salvaged by just making modifications to the helper logic and leaving the tests themselves largely unchanged. Andrew _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
