Skip to content
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.

Latest commit

 

History

History
98 lines (70 loc) · 3.54 KB

test-plan.md

File metadata and controls

98 lines (70 loc) · 3.54 KB
Raw

Test Plan

Test plan for Firefox Lockwise for iOS

See also: https://wiki.mozilla.org/QA/Mobile/LockboxiOSTestPlan

Overview

Firefox Lockwise for iOS is a new mobile iOS app developed with a pre-defined set of P1 "must have" requirements and a target release at the end of June in the Apple App Store and in Test Pilot.

Mozilla Product Integrity provides embedded QA to work with the team throughout the weekly sprints allowing for ongoing testing and feedback, issue triage, and continuous test plan development and end-to-end regression testing in order to accommodate a quick release schedule and submission to the App Store by end of May.

Ownership

  • Product Integrity: Catalin Suciu, Simion Basca, Isabel Rios
  • Product Manager: Sandy Sage
  • Engineering Manager: Devin Reams
  • Engineering Leads: Sasha Heinen, James Hugman, Matt Miller

Entry Criteria

  • PI has access to all product documentation, designs, code
  • The iOS app code is available on GitHub and builds:
    • locally via Xcode (Branch and Release)
    • on device via buddybuild (Branch and Release)
    • on device via TestFlight (Release)

Exit Criteria

  • All test suites against P1 "must have" features have performed
  • All bugs related to the P1 "must have" features have been triaged
  • All bugs resolved fixed have been verified

Test Matrix

  • Devices to be tested (no iPad):
    • iPhone X
    • iPhone 8 and 8 Plus
    • iPhone 7 and 7 Plus
    • iPhone SE
  • Major operating system versions to be tested (current and one prior):
    • iOS 11 (including point-release betas)
    • iOS 10

Test Suites

Accessibility

There are a number of best practices and accessibility features available to iOS developers and we intend to build and test for:

1. VoiceOver support

The reading of on-screen interface items and objects. Testing for:

  • All on-screen navigation and button titles are read
  • All on-screen alerts and popovers (interrupting the interface) are read
  • All labels and text elements on screen are read
  • Interaction elements like input boxes and filters have meaningful instructions
  • Links to open websites are clearly indicated and read

2. User interface design

The interface is legible and tappable by designing and testing for:

  • adequate color contrasts (e.g.: no light text on light background)
  • button and input sizes (e.g.: large enough to tap into easily and consistently)
  • text sizes follow system adjustment (i.e. respect "Larger Text" setting)

MVP Testing and Results documented at:
#441

Out of Scope

  1. Internal metrics/analytics review and testing (see metrics.md)
  2. Internal security review (performed separately)