352
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
v2.0 change
Oana.horvath (talk | contribs) |
(v2.0 change) |
||
| Line 3: | Line 3: | ||
= Intro/Summary/Notes = | = Intro/Summary/Notes = | ||
== Intro and Summary == | == Intro and Summary == | ||
* This wiki outlines the test requirements for Focus for Android | * This wiki outlines the test requirements for Focus for Android releases. | ||
* Use this generalized Test Plan as a starting point for creating Plans, Suites, and Cases | * Use this generalized Test Plan as a starting point for creating Plans, Suites, and Cases | ||
| Line 10: | Line 10: | ||
== Feature Lists == | == Feature Lists == | ||
For the list of features and its status, please refer to [https://github.com/mozilla-mobile/focus-android/projects/3 here]. | |||
'Aqua' label refers to the issues that are slated for the next upcoming release | |||
* | * NOTE: Focus for Android bugs are maintained in [https://github.com/mozilla-mobile/focus-android/issues Github] | ||
= Schedule = | = Schedule = | ||
* All features for | * All features for 2.0 should be completed by Aug 4th, 2017 to begin acceptance testing | ||
* Testing, including acceptance testing, should be completed by | * Testing, including acceptance testing, should be completed by Aug 10th, 2017. | ||
* Focus for Android is currently scheduled to be released | * Focus for Android 2.0 is currently scheduled to be released Aug 17th, 2017. | ||
= Personnel = | = Personnel = | ||
| Line 46: | Line 31: | ||
== QA Team == | == QA Team == | ||
* [https://phonebook.mozilla.org/?search/No-Jun%20Park No-Jun Park] | * [https://phonebook.mozilla.org/?search/No-Jun%20Park No-Jun Park] | ||
= Resource Plan = | = Resource Plan = | ||
| Line 53: | Line 37: | ||
= Test Strategy = | = Test Strategy = | ||
== 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 features will have corresponding test cases. | 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 features will have corresponding test cases. The test suite will be executed by Softvision for the acceptance testing. | ||
== Automated Tests == | == Automated Tests == | ||
Automation tests will be mainly used for quick regression check of key UI features. Overall, automation tests will be added to the same Github repo, and executed on [https://dashboard.buddybuild.com/apps/584f67f6f3d6eb01000842d6 BuddyBuild CI system]. While the unit tests will be run for each commit, UI Tests (in Espresso framework) will be executed in master branch only. The test result will be inspected for new failures, and github issue will be raised for tracking. | Automation tests will be mainly used for quick regression check of key UI features. Overall, automation tests will be added to the same Github repo, and executed on [https://dashboard.buddybuild.com/apps/584f67f6f3d6eb01000842d6 BuddyBuild CI system]. While the unit tests will be run for each commit, UI Tests (in Espresso framework) will be executed in master branch only. The test result will be inspected for new failures, and github issue will be raised for tracking. | ||
Automation tests are located [https://github.com/mozilla-mobile/focus-android/tree/master/app/src/androidTest here]. | Automation tests are located [https://github.com/mozilla-mobile/focus-android/tree/master/app/src/androidTest here]. | ||
| Line 87: | Line 58: | ||
== Test Deliverables == | == Test Deliverables == | ||
* Completed TestRail Test suite which covers all | * Completed TestRail Test suite which covers all features with UI aspects | ||
* Automated Test suite in master branch, running on every checkin | * Automated Test suite in master branch, running on every checkin | ||
* Github issues for every issue found | * Github issues for every issue found | ||
| Line 126: | Line 97: | ||
= Signoff/Exit Criteria = | = Signoff/Exit Criteria = | ||
* No critical or major UI bugs | * No critical or major UI bugs | ||
* No easily reproducible crashes | * No easily reproducible crashes | ||