352
edits
QA/Mobile/FirefoxTVTestPlan: Difference between revisions
Jump to navigation
Jump to search
→Process: further process update
(→Process: Process update) |
(→Process: further process update) |
||
| Line 35: | Line 35: | ||
= Test Strategy = | = Test Strategy = | ||
== Process == | == Process == | ||
* When the development work on github issue is completed, whether it is before/after code freeze, '''QA-ready''' label may be applied to | * When the development work on github issue is completed, whether it is before/after code freeze, '''QA-ready''' label may be applied to high-priority issues, indicating that they are available for testing. The issue should belong to a correct milestone before the development work can be started. | ||
* QA will verify the closed issues under the milestone, and upon completion, | * QA will verify the closed issues under the milestone, and upon completion, high priority issues will be marked with '''QA-approved''', removing '''QA-ready''' label. | ||
* If | * If a closed issue under the milestone is not QA verifiable, or worth the investment for testing time it can be marked with '''QA-denied''' | ||
* After code freeze, ideally, all issues should be marked with one of | * After code freeze, ideally, all closed issues that does not need QA activity should be marked with one of '''QA-denied'''. | ||
* After the QA | * After the QA sign off, it is implied that all closed issues that are not marked as '''QA-denied'''' has been verified by QA team. | ||
* This does not apply to metabugs. | * This does not apply to metabugs. | ||