TestEngineering/Web/Automation/Gaia UI Testing: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 27: Line 27:
### [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%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]
### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/job/b2g.inari.mozilla-central.ui/ Inari master]
###  
### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/job/b2g.inari.mozilla-b2g26_v1_2.ui/ Inari v1.2]
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 =
Confirmed users
425

edits

Navigation menu