Confirmed users
9,511
edits
QA/Execution/Web Testing/SUMO/Release Checklist: Difference between revisions
QA/Execution/Web Testing/SUMO/Release Checklist (view source)
Revision as of 18:19, 29 April 2010
, 29 April 2010no edit summary
No edit summary |
|||
| Line 39: | Line 39: | ||
'''Push day''' | '''Push day''' | ||
* Team is notified via IT push bug | * Team is notified via IT push bug of the push time - <font color="orange">IT lead</font> | ||
* IT pushes at the agreed-upon time and updates the bug and #sumodev channel of the changes | * IT pushes at the agreed-upon time and updates the bug and #sumodev channel of the changes | ||
* Dev/QA/IT agree it's stable to test - <strong>Entire SUMO dev team + IT</strong> | * Dev/QA/IT agree it's stable to test - <strong>Entire SUMO dev team + IT</strong> | ||
* QA begins testing fixed bugs and running a combination of Litmus tests + automation (eventually -- not there yet w/Kitsune) - <font color="green">QA lead</font> | * QA begins testing fixed bugs and running a combination of Litmus tests + automation (eventually -- not there yet w/Kitsune) - <font color="green">QA lead</font> | ||
* Once QA (and everyone) feels comfortable with the build, they verify the push bug - <font color="green">QA lead</font> | * Once QA (and everyone) feels comfortable with the build, they verify the push bug - <font color="green">QA lead</font> | ||