Confirmed users
1,477
edits
TestEngineering/UI/AMO/Test Plan/EntryExitCriteria: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/UI/AMO/Test Plan/EntryExitCriteria (view source)
Revision as of 04:11, 8 October 2012
, 8 October 2012→Exit Criteria
| Line 7: | Line 7: | ||
# All P1s, P2s, and Blocker and Critical bugs have been verified by QA or have been marked [qa-] as not needing verification | # All P1s, P2s, and Blocker and Critical bugs have been verified by QA or have been marked [qa-] 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.) | ##(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 | # QA has appraised WebDev either on IRC or through email of the testing performed, and the outstanding bug list | ||
# QA and development have assessed and vetted Moztrap-testrun failures | # QA and development have assessed and vetted Moztrap-testrun failures | ||
# Stakeholders from QA,development and Product have met to discuss the pre-release readiness of the release. | # Stakeholders from QA,development and Product have met to discuss the pre-release readiness of the release. | ||