<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 10-12-2018 22:32, Claudio Luck
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:44fed894-9ee0-49b7-4601-982e8e01693f@pep.foundation">
<pre class="moz-quote-pre" wrap="">On 10.12.18 15:15, leon lee wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> * create tests to automate measuring of UI operational performance
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
What should one do to start with automated UI testing of extensions?
Mozmill, which is still used by Thunderbird, has been phased out in
Firefox. But its successor Marionnette/Puppeteer has not landed yet in
Thunderbird releases (or has it?). Chasing documentation about any of
these specifically in regards to Thunderbird quickly redirects into
generic Mozilla land, becoming very confusing.</pre>
</blockquote>
<p>Geoff has been working on enabling <a moz-do-not-send="true"
href="https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Mochitest">Mochitests</a>
for Thunderbird. There are patches basically ready to go to, and
we expect them to run on our CI infrastructure soon. Some
mochitests for WebExtension API functionality have already landed
in tree and can be run locally (with some patches applied). <br>
</p>
<p>IIUIC, the Mochitest test suite uses Marionette for communicating
with Thunderbird. Whether to use Mozmill tests or Mochitests
depends on how quickly you need to get going. Mozmill isn't going
away anytime soon as we can't migrate the tests very easily, but
in general Mochitests are likely preferable.<br>
</p>
<p>I agree the documentation quickly becomes confusing for
Thunderbird specifics, and this is something we should address.<br>
</p>
<p> -Magnus<br>
</p>
<p><br>
</p>
</body>
</html>