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.

To finally get rid of that I was working all the last weeks to make the
following changes:

* Added mozharness scripts for executing firefox-ui-tests and enhanced
base mozharness modules to cope with various other feature requirements
we had.

* Moved our tests into mozilla-central under testing/firefox-ui/ and
updated test packaging. Backports happened down to Firefox 45.0 so that
we will benefit from the upcoming ESR release too.

* Updated mozmill-ci (which now runs our firefox-ui-tests) to use test
packages across all supported branches down to current Firefox 45.0ESR.
With that we can finally get rid of our Github repository. It turned out
to not be an easy process given that we do not only run our tests
against en-US but also a couple of other locales for nightly and release
builds. So a couple of blockers had to be fixed side-by-side in
packaging, build notifications via Mozilla Pulse etc.

* Added support for TaskCluster to run our tests once the build has been
finished. Similar to other tests this only works for linux64 debug right
now. Test results can be found on Treeherder in the Fxfn group. Keep in
mind that those are still Tier-3, so you will have to make those tests
visible. If you have to make changes to our tests and want to push to
try, simply use '-u firefox-ui-functional,firefox-ui-functional-e10s' in
the try comment (trychooser will be updated soon).

With all the above close to be done now, I'm starting to write
documentation. This will enable us to push results as Tier-2, and also
have a base set for contributors to get started hacking on our tests.

If you have questions please ask or join our #automation channel on IRC.

Cheers,
Henrik
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to