352
edits
QA/Mobile/FocusAndroidTestPlan: Difference between revisions
Jump to navigation
Jump to search
First draft
(→Development: fix) |
(First draft) |
||
| 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 V1. | ||
* 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 29: | Line 29: | ||
* NOTE: Focus for Android bugs are maintained in [https://github.com/mozilla-mobile/focus-android/issues Github] | * NOTE: Focus for Android bugs are maintained in [https://github.com/mozilla-mobile/focus-android/issues Github] | ||
* ([https://github.com/mozilla-mobile/focus-android/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3Av1.0%20is%3Aissue%20label%3Afeature%20 List of complete P1 features]) | * ([https://github.com/mozilla-mobile/focus-android/issues?utf8=%E2%9C%93&q=is%3Aissue%20label%3Av1.0%20is%3Aissue%20label%3Afeature%20 List of complete P1 features in Github]) | ||
= Schedule = | = Schedule = | ||
* All features for V1 should be completed by | * All features for V1 should be completed by June 9th, 2017 to begin acceptance testing | ||
* Testing should be completed by June | * Testing, including acceptance testing, should be completed by June 14th, 2017. | ||
* Focus for Android is scheduled to be released June | * Focus for Android is scheduled to be released June 20th, 2017. | ||
= Personnel = | = Personnel = | ||
| Line 47: | Line 47: | ||
= Resource Plan = | = Resource Plan = | ||
* Each QA person will | * Each QA person will be 40% allocated to this project | ||
= Test Strategy = | = Test Strategy = | ||
== Manual Tests == | == Manual Tests == | ||
UI Test suite for Focus for Android will be located in TestRail ( | UI Test suite for Focus for Android will be located in TestRail (Link TBD). As a minimum, each of the P1 features will have corresponding test cases. | ||
== Automated Tests == | == Automated Tests == | ||
| Line 68: | Line 68: | ||
* Custom tabs (Pending) | * Custom tabs (Pending) | ||
* Check notification while browsing session is active (Pending) | * Check notification while browsing session is active (Pending) | ||
Automation tests are located [https://github.com/mozilla-mobile/focus-android/tree/master/app/src/androidTest here]. | |||
In addition to regularly run automated tests, QA will also generate screenshots for [https://l10n.mozilla-community.org/webstatus/?product=focus-android l10n verification]. | In addition to regularly run automated tests, QA will also generate screenshots for [https://l10n.mozilla-community.org/webstatus/?product=focus-android l10n verification]. | ||
== Code Analysis == | == Code Analysis == | ||
[https://codecov.io/gh/mozilla-mobile/focus-android/branch/master Codecov] is added to the github repo, and will display increase/decrease of unit test code coverage | * [https://codecov.io/gh/mozilla-mobile/focus-android/branch/master Codecov] is added to the github repo, and will display increase/decrease of unit test code coverage | ||
* Findbugs addon is added to warn developers against possible code issues, as well as Lint. | |||
== Outside Scope == | == Outside Scope == | ||
| Line 79: | Line 82: | ||
* Performance Tests | * Performance Tests | ||
* Localization Tests | * Localization Tests | ||
* Beta testing with a wider audience | |||
== Test Deliverables == | == Test Deliverables == | ||
* Completed TestRail Test suite which covers all P1 features with UI aspects | |||
* Automated Test suite in master branch, running on every checkin | |||
* Github issues for every issue found | |||
* Manual acceptance test report | |||
* Signoff Decision | |||
= Dependencies/Risks = | = Dependencies/Risks = | ||
* Since the blocking status of trackers is not exposed via adb log or UI, its validation will rely on unit tests | |||
* The performance of Focus for Android is not measured precisely, will rely on the tester feedback | |||
* The automation/manual test suites will be built incrementally as new features are added to Github, and the late features may not be exposed to validation as much as earlier ones. The acceptance test after the feature completion date will be performed with the special emphasis on 1. key features and 2. most recently added features | |||
= Signoff/Exit Criteria = | = Signoff/Exit Criteria = | ||
* No open v1.0 bugs, which impacts the security and key operations of the app | |||
* No UI bugs | |||