352
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
QA/Mobile/FocusAndroidTestPlan (view source)
Revision as of 21:57, 7 November 2017
, 7 November 2017→Test Strategy: test process defined
(→Automated Tests: espresso -> espresso/UIAutomator) |
(→Test Strategy: test process defined) |
||
| Line 37: | Line 37: | ||
= Test Strategy = | = Test Strategy = | ||
== Process == | |||
* When the development work on github issue is completed, whether it is before/after code freeze, '''ReadyForQA''' label will be applied so 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 issue, and upon completion, it'll be marked with '''VerifiedByQA''', removing '''ReadyForQA''' label. | |||
* If an issue is not QA verifiable, it can be marked with '''QANotNeeded''' | |||
* After code freeze, ideally, all issues should be marked with either '''ReadyForQA''', '''VerifiedByQA''', or '''QANotNeeded'''. | |||
* After the QA signoff, ideally, all issues should be marked with '''VerifiedByQA''', or '''QANotNeeded'''. | |||
* The issue can be closed after it is marked as '''VerifiedByQA''', or '''QANotNeeded''' | |||
* This does not apply to metabugs. | |||
== Manual Tests == | == Manual Tests == | ||
UI Test suite for Focus for Android will be located in [https://testrail.stage.mozaws.net/index.php?/suites/overview/48 TestRail]. As a minimum, each of the P1 UI features will have corresponding test cases. The test suite will be executed by Softvision for the acceptance testing. | UI Test suite for Focus for Android will be located in [https://testrail.stage.mozaws.net/index.php?/suites/overview/48 TestRail]. As a minimum, each of the P1 UI features will have corresponding test cases. The test suite will be executed by Softvision for the acceptance testing. | ||