QA/Mobile/FirefoxTVTestPlan: Difference between revisions

→‎Process: process change
(→‎QA Team: personnel change)
(→‎Process: process change)
Line 27: Line 27:
= 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 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/QA work can be started.
* QA will verify the closed issues under the milestone, and upon completion, issues will be marked with '''QA-approved''' label.
* QA will verify the appropriate closed issues under the milestone, and upon completion, issues will be marked with '''QA-approved''' label and/or moved to "QA Verified" column in the project dashboard.
* 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.
* 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 marked as '''QA-approved'''' and/or in "QA Verified" column in the project dashboard has been verified by QA team.
* This does not apply to metabugs.
* This does not apply to metabugs.
* For sprint status, please refer to the [https://github.com/orgs/mozilla-mobile/projects/27 Firefox TV project dashboard].
* For QA Criteria, please see [[QA/Mobile/FocusAndroidTestPlan#QA_Criteria|Focus Android QA Criteria]]
* For QA Criteria, please see [[QA/Mobile/FocusAndroidTestPlan#QA_Criteria|Focus Android QA Criteria]]


352

edits