This page isn't finished yet.
Your feedback to firstname.lastname@example.org would be greatly appreciated.
The main repository is currently in github: Mozilla-b2g/gaia. Look under the gaia/tests/python/gaia-ui-tests/ for the gaia-ui-tests specific code. Due to Taiwan's local test needs, we also have another repository synchronized with main repository: Mozilla-TWQA/gaia-ui-tests. Before you start a new area of test script writing, you might want to look into Mozilla-TWQA/gaia-ui-tests to see if they have something ready for you already.
Running and Writing Tests
- Environment Setup
- What you'll need and need to do before you run or write the gaiatest the first time.
- Tests Running
- How to run the gaiatest.
- Tests Writing
- How to write the tests for gaiatest.
- Function Reference
Marionette method overview
shortcut to "Basic Action" part
shortcut to "Action Chain" part
Gaia-ui-test method overview (note that this is only draft now)
Gaia-ui-test apps overview
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 of Mozilla-b2g/gaia open issues.
Email to email@example.com. Or, find us on irc at channels #ateam, #mozwebqa, and #moztpeqa.