Confirmed users
425
edits
TestEngineering/Web/Automation/Gaia UI Testing: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Web/Automation/Gaia UI Testing (view source)
Revision as of 03:03, 19 November 2013
, 19 November 2013no edit summary
No edit summary |
|||
| Line 11: | Line 11: | ||
Either add documentation for this here, or link to existing documentation, which I believe is currently in the Github repo. | Either add documentation for this here, or link to existing documentation, which I believe is currently in the Github repo. | ||
= Monitoring Jenkins Jobs For Failures and XPasses = | |||
The first priority, when supporting Gaia UI Testing, is to ensure that our existing tests are accurate and reliable. To that end, we need to monitor the jobs that run in our CI and address any that are failing or are xpassing (passing but marked as expected to fail). | |||
To review the jobs for failures and xpasses, complete the following steps: | |||
# Choose the job to review. This involves choosing the branch and device. | |||
## Which branch to review? | |||
### We currently run jobs against the [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Master/ master] and [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20v1.2/ v1.2] branches of Gaia. When reviewing the job results for failures and xpasses, always review master first, and then v1.2. | |||
## Which device to review? | |||
### We currently run jobs on two different devices, [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/ Hamachi] and [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/ Inari]. When reviewing the job results for failures and xpasses, always review Hamachi first, and then Inari. | |||
## Taking the above into consideration, the order for review should be: | |||
### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Master/job/b2g.hamachi.mozilla-central.ui/ Hamachi master] | |||
### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-b2g26_v1_2.ui/ Hamachi v1.2] | |||
### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/job/b2g.inari.mozilla-central.ui/ Inari master] | |||
### | |||
and [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20v1.2/job/b2g.inari.mozilla-b2g26_v1_2.ui/ b2g.inari.mozilla-b2g26_v1_2.ui]. | |||
## Choose the device. We currently run jobs on two different devices, which also have tabs in Jenkins. These are [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/ Hamachi] and [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/ Inari]. | |||
The second element of the job name, in this case ''hamachi'' and ''inari'') refers to the physical device on which the tests are run. | |||
* [https://github.com/mozilla-b2g/gaia/tree/master/tests/python/gaia-ui-tests Master] - this is the current development branch of Gaia and is priority #1 for failing tests. All new development (e.g., new tests) should be completed in the master branch and then, if necessary, uplifted to other branches of interest. | |||
* [https://github.com/mozilla-b2g/gaia/tree/v1.2/tests/python/gaia-ui-tests v1.2] - this is the next shipping version of Gaia, and is priority #2 for failing tests. Changes should only be committed to v1.2 if they either: | |||
** land first in master and are deemed necessary for v1.2, or | |||
** contain fixes that are specific to v1.2 | |||
= Keeping Branches in Sync with Master = | = Keeping Branches in Sync with Master = | ||