352
edits
QA/Mobile/FirefoxTVTestPlan: Difference between revisions
→Process: process update
(→QA Team: Levente added) |
(→Process: process update) |
||
| Line 37: | Line 37: | ||
== 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 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. | * 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, issues will be marked with '''QA-approved''' label. | ||
* If a closed issue under the milestone is not QA verifiable, or worth the investment for testing time | * If a closed issue under the milestone is not QA verifiable, or worth the investment for testing time any QA label applied will be removed and left in closed state. | ||
* After the QA sign off, it is implied that all closed issues that are marked as '''QA-approved'''' has been verified by QA team. | |||
* After the QA sign off, it is implied that all closed issues that are | |||
* This does not apply to metabugs. | * This does not apply to metabugs. | ||