352
edits
QA/Mobile/FirefoxTVTestPlan: Difference between revisions
→Process: Process update
(→Process: 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 | * When the development work on github issue is completed, whether it is before/after code freeze, '''QA-ready''' label may be applied to indicate that the issue is available for testing. The issue should belong to a correct milestone before the development work can be started. | ||
* QA will verify the | * QA will verify the closed issues under the milestone, and upon completion, it'll be marked with '''QA-approved''', removing '''QA-ready''' label. | ||
* If an issue is not QA verifiable, or worth the investment for testing time it can be marked with '''QA-denied''' | * If an 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 | * After code freeze, ideally, all issues should be marked with one of '''QA-ready''', '''QA-approved''', or '''QA-denied'''. | ||
* After the QA signoff, ideally, all issues should be marked with '''QA-approved''', or '''QA-denied'''. | * After the QA signoff, ideally, all issues should be marked with either '''QA-approved''', or '''QA-denied'''. | ||
* This does not apply to metabugs. | * This does not apply to metabugs. | ||