Matthew N. wrote on 03/01/2016 06:18 PM:
> 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.
So Andrew already told a lot, and just to emphasize here we really do
not w
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 l
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 r
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. Bes
4 matches
Mail list logo
