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:21, 19 November 2013
, 19 November 2013→Monitoring Jenkins Jobs For Failures and XPasses
| Line 24: | Line 24: | ||
### 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. | ### 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: | ## 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%20Master/job/b2g.hamachi.mozilla-central.ui/lastCompletedBuild/testReport/ 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%20Hamachi/job/b2g.hamachi.mozilla-b2g26_v1_2.ui/lastCompletedBuild/testReport/ 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/lastCompletedBuild/testReport/ Inari master] | ||
### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/job/b2g.inari.mozilla-b2g26_v1_2.ui/ Inari v1.2] | ### [http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Inari/job/b2g.inari.mozilla-b2g26_v1_2.ui/lastCompletedBuild/testReport/ Inari v1.2] | ||
# Review the results of the latest run of the job in question. | |||
## Review failures. | |||
### You can use the links above to view the latest results of the job. This will give you a quick summary of which tests are currently failing. Looking at the ''Age'' of the failure will give you an idea of whether this is a new failure, or one that has been happening for awhile. Also, failures with an ''Age'' of 1 often indicate intermittent failures. | |||
### For each failure that you find: | |||
#### Search for a bug in Bugzilla that has been opened for the failure. Every failure that needs to be addressed must have a bug opened for it. If you find an open bug for a failure, examine it: | |||
##### If it has a pull request attached to it which is waiting to be reviewed, review it. A pull request that is waiting to be reviewed is one that has no negative reviews and less than two positive reviews. | |||
##### If it is unassigned, and you would like to take the time to address it, assign it to yourself and update its status to ''Assigned''. Do not do this unless you have the time to address it. | |||
#### If you do not find an open bug for the failure, open one and include as much detail about the failure as possible. | |||
##### If you have time to address the failure, assign it to yourself and update its status to ''Assigned''. | |||
## Review xpasses. | |||
### You can also use the links above to view the latest results of the job, but this summary will not show you which jobs are xpassing. To do that you need to view the . This will give you a quick summary of which tests are currently failing. Looking at the ''Age'' of the failure will give you an idea of whether this is a new failure, or one that has been happening for awhile. Also, failures with an ''Age'' of 1 often indicate intermittent failures. | |||
### For each failure that you find: | |||
#### Search for a bug in Bugzilla that has been opened for the failure. Every failure that needs to be addressed must have a bug opened for it. If you find an open bug for a failure, examine it: | |||
##### If it has a pull request attached to it which is waiting to be reviewed, review it. A pull request that is waiting to be reviewed is one that has no negative reviews and less than two positive reviews. | |||
##### If it is unassigned, and you would like to take the time to address it, assign it to yourself and update its status to ''Assigned''. Do not do this unless you have the time to address it. | |||
#### If you do not find an open bug for the failure, open one and include as much detail about the failure as possible. | |||
##### If you have time to address the failure, assign it to yourself and update its status to ''Assigned''. | |||
= Keeping Branches in Sync with Master = | = Keeping Branches in Sync with Master = | ||