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 want to work with any JS globals etc when navigating through the ui but always use ui elements directly. The reason is that we also run our tests with a couple of other locales and for each of those the command, access keys and others can differ. The before mentioned firefox-puppeteer library is a helper to make test creation even more easier. So you don't have to remember the real DOM id, label, anon attribute or what-ever when accessing such elements. We have a nice hierarchy like: self.browser.navbar.back_button.click() The number of tests are still low given that we haven't had the time to port more tests from mozmill. That means as of now we have converted only the most important tests including remote security checks for various protocols and some locationbar and privatebrowsing tests. We would like to get more tests added especially those which would require a restart of Firefox, or those for testing shortcuts etc across locales. So we hope that you all might want to create one in case you have a need for. > Could you also add a description to > https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing? Yes I will and this is actually one of my remaining goals this quarter. The work for that will be tracked on bug 1237552. In case you want to know more about the code right now, you can find everything here: http://mxr.mozilla.org/mozilla-central/source/testing/puppeteer/firefox/ http://mxr.mozilla.org/mozilla-central/source/testing/firefox-ui/ Let me know if there are still open questions. -- Henrik _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
