Add-ons/QA/Testplan/NewAMOMobile

Overview

The completely new AMO Mobile page design with a modern and simplified look, oriented to users and ease of utilization.

Purpose

A more attractive mobile AMO page with a more easy and intuitive way to install and search for Add-ons and Themes

Entry Criteria

• QA has access to mocks : https://mozilla.invisionapp.com/share/GY8O3Z4ZE#/screens . Any other info were found in bugs logged in GitHub
• The feature has landed in -dev : https://addons-dev.allizom.org/en-US/firefox/ and will land in prod in mid February. Aiming for Feature complete End of Jan

Exit Criteria

• All related bugs triaged
• All blockers fixed
• All resolved bugs verified by QA
• Found-fixed bugs rate going down in time

Scope

what's in scope?

• AMO mobile appearance.
• Behavior of AMO mobile in logged in \ logged out states
• Inatall\Uninstall of Add-ons and Themes on Mobile
• Search for Add-ons and Themes on Mobile. Sorting the search results. Search suggestions
• Add-on and Themes reviews and rating on Mobile
• Add-ons and Themes categories
• AMO mobile in different languages and RTL view
• Collections in AMO mobile - not sure if this will be implemented but this is present on mocks
• Versions availability in AMO mobile public pages
• Themes preview on Mobile
• User settings on Mobile
• Page errors

what's out of scope?

• Add-ons functionality
• Translations in different languages . This will not exclude testing on another languages for UI issues related to different length of strings

Ownership

Product Manager: Matthew Riley MacPherson; irc nick :tofumatt
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: Rares Macarie; irc nick :RaresM
Add-ons QA: Cosmin Badescu; irc nick :CosminB

Requirements for testing

Environments

• Android phone, tablets

Servers

• Stage: https://addons.allizom.org/en-US/
• Dev: https://addons-dev.allizom.org/en-US/
• Production: https://addons.mozilla.org/en-US/

Channels

• Release
• Nightly
• Unbranded builds

Test Strategy

Test Execution Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase	Start Date	End Date
Start project	11.01.2016
Study PRD/mocks received	11.01.2017
QA - Test plan creation	30.01.2017	31.01.2017
QA - Test cases preparation	30.01.2017	01.02.2017
QA - Test cases execution	01.02.2017	15.02.2017
Release Date	16.02.2017

Testing Tools

Process	Tool
Test plan creation	Mozilla wiki
Test case creation	[TBD TestRail] / Google docs
Test case execution	[TBD TestRail]
Bugs management	Github

References

* PRD - https://mozilla.invisionapp.com/share/GY8O3Z4ZE#/screens
* Tracker: 3465

Testcases

Test Areas

• AMO Mobile

Test suite

Gdoc Test suite - Link
TestRail - TBD

Bug Work

• All Feature bugs:
  • Open V1
  • Closed V1
  • Open V2
  • Closed V2

Bug fix verification

• Verified Fixed V1

Sign off

Criteria

Check list

• All test cases should be executed
• All blockers must be fixed and verified or have an agreed-upon timeline for being fixed