This page isn't finished yet.
Your feedback to firstname.lastname@example.org would be greatly appreciated.
Gaia-ui-tests uses gaiatest, a Python package based around Marionette. Gaiatest is designed to wrap HTML locators, Marionette calls and API calls into common . Marionette is based on the W3C standard developed for Selenium WebDriver - if you have used WebDriver and page objects before then you will find using Marionette and gaiatest easy.
Running and Writing Tests
- Environment Setup
- What you'll need and need to do before you run or write the gaiatest the first time.
- Running Tests
- Running gaia-ui-tests against device and desktopb2g in a variety of configurations.
- Gathering Power Draw
- How to use gaiatest to log power draw while a test is running
There are two categories of bugs when using gaia-ui-tests; marionette related or gaia-ui-tests related. It's kind of ambiguous to distinguish between these two. However, you can follow the basic rules:
1. Marionette related bugs: If there are connection issues, marionette command not recognized, or tests that started to fail without much change in gaia, this might be a marionette related bug. Before you report the bug, make sure it's not because of your unupdated marionette client/server.
*You can also view a list of current bugs to see if your problem is already being addressed. Report bug in bugzilla is the best way to do so.
2. Gaia-ui-tests: When tests started to fail without much changes in gaia and marionette client, it might be gaia-ui-tests bug.
*You can view bugs or report bugs in github at Mozilla-b2g/gaia.
Email to email@example.com. Or, find us on irc at channels #ateam, #mozwebqa, and #moztpeqa.