Confirmed users
2,177
edits
QA/Execution/Web Testing/roles/buildmaster: Difference between revisions
QA/Execution/Web Testing/roles/buildmaster (view source)
Revision as of 17:15, 23 April 2015
, 23 April 2015no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
= | =Buildmaster= | ||
Create a set of guidelines for investigating failures in our public Jenkins instance. This would be used by whoever is monitoring for failures, but would also be valuable for community who want to dive in. It should include how to identify failures, how to determine if they're already known, how to replicate them locally, how to determine if they're application bugs or test bugs, where to raise them, who to notify, and even how to fix them (if they're test failures) and submit pull requests. This could form part of a boot camp similar to other teams. -- from our 2015, [https://etherpad.mozilla.org/webqa-goals-2015-q2 Q2 goals brainstorm]. | Create a set of guidelines for investigating failures in our public Jenkins instance. This would be used by whoever is monitoring for failures, but would also be valuable for community who want to dive in. It should include how to identify failures, how to determine if they're already known, how to replicate them locally, how to determine if they're application bugs or test bugs, where to raise them, who to notify, and even how to fix them (if they're test failures) and submit pull requests. This could form part of a boot camp similar to other teams. -- from our 2015, [https://etherpad.mozilla.org/webqa-goals-2015-q2 Q2 goals brainstorm]. | ||
| Line 13: | Line 13: | ||
==Role Definition== | ==Role Definition== | ||
* | * buildmaster role last 2 weeks | ||
* edit jenkins desc with your name as buildmaster | * edit jenkins desc with your name as buildmaster | ||
* | * buildmaster is point of contact for open issues/bugs | ||
* role includes filing bugs/issues, sending out emails, investigating issues | * role includes filing bugs/issues, sending out emails, investigating issues | ||
* does NOT include escalation paths, prioritizing fixes, following up with other teams | * does NOT include escalation paths, prioritizing fixes, following up with other teams | ||
| Line 113: | Line 113: | ||
* could make a public job for contributors to workon or fix | * could make a public job for contributors to workon or fix | ||
* https://bugzilla.mozilla.org/enter_bug.cgi?product=quality.mozilla.org | * https://bugzilla.mozilla.org/enter_bug.cgi?product=quality.mozilla.org | ||
==FAQ== | |||
===Who do I contact if the issue is related to Persona?=== | |||
If you trace an issue to Persona (the sign-on service) you should contact :jrgm in #persona. You can also raise issues in the project's [https://github.com/mozilla/persona/issues GitHub repository]. | |||
===Why is the failure only happening on Sauce Labs?=== | |||
It could be that the failure is only presenting itself on specific browser window sizes. Sauce Labs uses virtual machines with screen resolutions that may differ from our internal Selenium Grid. You could try specifying a browser window size to make the results consistent, or at least consider how the size of the browser might affect the tests that are failing. | |||