Confirmed users
9,511
edits
QA/Execution/Web Testing/SUMO/Test Plan: Difference between revisions
QA/Execution/Web Testing/SUMO/Test Plan (view source)
Revision as of 09:28, 16 October 2009
, 16 October 2009→Release Criteria
| Line 23: | Line 23: | ||
# 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 | ||
## (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 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 | ||
# 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 and development have assessed and vetted Litmus-testrun failures | # QA and development have assessed and vetted Litmus-testrun failures | ||