QA/Mobile/FocusiOSTestPlan: Difference between revisions
< QA
(→Intro and Summary: remove mentioning of version) |
(→Test Strategy: new process) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
== Feature Lists == | == Feature Lists == | ||
For the list of features for any particular upcoming milestones, please see [https://github.com/mozilla-mobile/focus-ios/projects/1 Github] | |||
= Schedule = | = Schedule = | ||
Please refer to [https://wiki.mozilla.org/Mobile/Focus/iOS/Train_Schedule Wiki] for 2017 release schedule | |||
= Personnel = | = Personnel = | ||
| Line 28: | Line 18: | ||
* [https://phonebook.mozilla.org/?search/Barbara%20Bermes Barbara Bermes] | * [https://phonebook.mozilla.org/?search/Barbara%20Bermes Barbara Bermes] | ||
== Development == | == Development == | ||
* [https://phonebook.mozilla.org/?search/jboek Jeff Boek] | |||
* [https://phonebook.mozilla.org/?search/bmunar Bryan Munar] | |||
* [https://phonebook.mozilla.org/?search/Susheel%20Daswani Susheel Daswani] | * [https://phonebook.mozilla.org/?search/Susheel%20Daswani Susheel Daswani] | ||
== 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] | ||
| Line 37: | Line 30: | ||
= Test Strategy = | = Test Strategy = | ||
== Process == | |||
We follow identical process as [https://wiki.mozilla.org/QA/Mobile/FocusAndroidTestPlan#Process Focus Android] | |||
== Manual Tests == | == Manual Tests == | ||
UI Test suite for Focus for iOS will be located in [https://testrail.stage.mozaws.net/index.php?/suites/overview/27 TestRail]. As a minimum, each of the UI features will have corresponding test cases. | UI Test suite for Focus for iOS will be located in [https://testrail.stage.mozaws.net/index.php?/suites/overview/27 TestRail]. As a minimum, each of the P1 UI features will have corresponding test cases. | ||
== 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/58cc46bc5753e401002f47b4 BuddyBuild CI system]. | 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/58cc46bc5753e401002f47b4 BuddyBuild CI system]. 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-ios/tree/master/XCUITest here]. | Automation tests are located [https://github.com/mozilla-mobile/focus-ios/tree/master/XCUITest here]. | ||
| Line 64: | Line 56: | ||
* Github issues for every issue found | * Github issues for every issue found | ||
* Signoff Decision | * Signoff Decision | ||
= Dependencies/Risks = | = Dependencies/Risks = | ||
Latest revision as of 22:06, 7 November 2017
This is the Test Plan for Focus for ios (https://github.com/mozilla-mobile/focus)
Intro/Summary/Notes
Intro and Summary
- This wiki outlines the test requirements for Focus for iOS.
- Use this generalized Test Plan as a starting point for creating Plans, Suites, and Cases
Feature Lists
For the list of features for any particular upcoming milestones, please see Github
Schedule
Please refer to Wiki for 2017 release schedule
Personnel
Program Management
Product Management
Development
QA Team
Resource Plan
- Each QA person will be 30% allocated to this project
Test Strategy
Process
We follow identical process as Focus Android
Manual Tests
UI Test suite for Focus for iOS will be located in TestRail. As a minimum, each of the P1 UI features will have corresponding test cases.
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 BuddyBuild CI system. The test result will be inspected for new failures, and github issue will be raised for tracking.
Automation tests are located here.
Code Analysis
- Codecov is added to the github repo, and will display increase/decrease of unit test code coverage
Outside Scope
Following tests are outside the scope of the QA:
- Unit Tests
- Performance Tests
- Localization Tests, including screenshot generation
- Beta testing with a wider audience
Test Deliverables
- Completed TestRail Test suite which covers all UI features
- Automated Test suite in master branch, running on every checkin
- Github issues for every issue found
- Signoff Decision
Dependencies/Risks
- Since the blocking status of trackers is not exposed, its validation will rely on manual tests
- The performance of Focus for iOS 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
- No regression bugs of existing features, which impacts the security and key operations of the app
- No critical or major UI bugs
- No easily reproducible crashes