QA/Mobile/FocusAndroidTestPlan

This is the Test Plan for Focus for Android (https://github.com/mozilla-mobile/focus-android)

Intro/Summary/Notes

Intro and Summary

• The following document/wiki outlines the "catch-all" test requirements for Focus for Android V1.
• Use this generalized Test Plan as a starting point for creating Plans, Suites, and Cases

Notes

• FAQs

Feature Lists

• "Must" P1 features:
  • Provide tracking-free browsing experience
  • Erase browsing history
  • Enable/Disable blocking of different types of trackers
  • Onboarding, we will highlight features that we believe will bring retention
  • Per session blocking
  • Custom tabs (scoped down)
  • Show notification while browsing session is active
  • Create localized completion list
  • Setting to allow screenshots
  • Support app shortcuts API

• P2 (if time permits, in order of priority)
  • Show number of ads/trackers blocked (4)
  • Locale switcher for Android (5)
  • Allow saving images in a website (4)
  • Add "search" action into text selection of third-party apps (3)

• NOTE: Focus for Android bugs are maintained in Github
• (List of complete P1 features)

Schedule

• All features for V1 should be completed by May 31st, 2017 to begin acceptance testing
• Testing should be completed by June 6th, 2017.
• Focus for Android is scheduled to be released June 12th, 2017.

Personnel

Program Management

• Barbara Bermes

Development

• Sebastian Kaspari
• Andrzej Hunt

== QA Team =-

• No-Jun Park
• Aaron Train

Resource Plan

• Each QA person will have 40% allocation to this project

Test Strategy

Manual Tests

UI Test suite for Focus for Android will be located in TestRail (Insert Link). As a minimum, each of the P1 features will have their 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. 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.

Following automation test cases will be added by end of the May:

• Accessing badly formed URL
• Accessing each of pull-down menu items
• Accessing simple webpages
• Changing search engine
• Checking for overall appearance
• Deleting browsing history
• Quick check of URL autocompletion
• Quick check of webview data deletion
• Quick check of Onboarding dialog (Pending)
• Custom tabs (Pending)
• Check notification while browsing session is active (Pending)

In addition to regularly run automated tests, QA will also generate screenshots for l10n verification.

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

Signoff/Exit Criteria

= References