They're more like end-to-end tests than browser-chrome. E.g instead of
calling Gecko APIs, they'll send a mouse event to a button, send key
events to a textbox, etc. So they'll theoretically perform actions
closer to what a user might do.
Since they're written in python, they can also do things like restart
the browser within the test (for e.g testing updates). It uses a library
called Firefox Puppeteer that's built on top of marionette-client:
http://firefox-puppeteer.readthedocs.org/en/latest/
(which lives in testing/puppeteer despite what the docs say)
Henrik can probably go into more details on what is tested.
-Andrew
On 01/03/16 12:18 PM, Matthew N. wrote:
CC: firefox-dev
On 2016-03-01 5:17 AM, Henrik Skupin wrote:
Over the last years the formerly known Mozmill tests and now Firefox ui
tests have been located in their own repository. That meant that we
always got regressions due to changes developers have been made in
Firefox. Hunting down those regressions and fixing them was always a
time consuming job. Beside all that we were also responsible for merging
our branches accordingly to our 6 week cycle.
Hi Henrik, thanks for sharing.
Could you give an overview of what is tested by this suite and how it
differs from mochitest-browser-chrome? It seems one difference is that
some(?) tests run on non-en-US.
Could you also add a description to
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing?
Thanks,
Matthew N. (:MattN)
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
