QA/Execution/Web Testing/SUMO/Test Plan: Difference between revisions

QA/Execution/Web Testing/SUMO/Test Plan (view source)

No change in size , 16 October 2009

Confirmed users

9,511

edits

@@ Line 19: / Line 19: @@
 ==Release Criteria==
-* QA has access to a staging server
+# QA has access to a staging server
-* All P1s, P2s, and Blocker and Critical bugs have been verified by QA or have been agreed upon as not needing verification
+# All P1s, P2s, and Blocker and Critical bugs have been verified by QA or have been agreed upon as not needing verification
-* QA has met with or emailed to Web Development (and in some cases, Marketing, Evangelism, etc.) the latest test plan for the current release
+# QA has met with or emailed to Web Development (and in some cases, Marketing, Evangelism, etc.) the latest test plan for the current release
-** (This gives us leeway in cases where, say, there are critical backend bugs that development files but we can't verify easily, or it's not needed.)
+## (This gives us leeway in cases where, say, there are critical backend bugs that development files but we can't verify easily, or it's not needed.)
-* QA has apprised WevDev either on IRC or through email of the testing performed, and the outstanding bug list
+# QA has apprised WevDev either on IRC or through email of the testing performed, and the outstanding bug list
-* QA signs off on the release
+# QA signs off on the release
-* QA assigns an engineer for the push
+# QA assigns an engineer for the push
 ==How you can help==