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

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

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

Bug fix verification
  • 4081 - Last step of new file submission mentions "version" submission
  • 4134 - "Lastest version" or "Latest version" ?
  • 3704 - Hide unreviewed versions (if there is at least one reviewed version) on the 'all versions' page
  • 4302 - Misleading info while adding a second beta-listed version for an unlisted add-on
  • 4269 - "Incomplete" status for unlisted add-ons in Dev Hub homepage
  • 4395 - Direct links to beta versions are broken
  • 4282 - Click on incomplete status redirects to final step of submission
  • 4245 - Add-on admin page should point to review-unlisted pages when relevant
  • 4024 - Setting an add-on waiting for approval to invisible leaves it with incorrect add-on status
  • 318 - Old version addon links broken, only static link to latest available
  • 4394 - "Completed" add-on is displayed as incomplete
  • 4282 - Click on incomplete status redirects to final step of submission
  • 4420 - Blocking submission for second listed version in 6 steps
  • 4245 - Add-on admin page should point to review-unlisted pages when relevant
  • 4398 - the (AMO) and (Self) tags aren't localised
  • 4022 - Error displayed while adding a developer reply for second unlisted version of an add-on
  • 4479 - Add-on unlisted review page is returning 500 error for add-ons with mixed unlisted/listed versions
  • 4484 - Search in "All Unlisted Add-ons" is not working for add-on with mixed versions if first version is unlisted
Logged bugs
  • 4217 - Beta-channel tooltip from beta-version submission step is not aligned
  • 4220 - Different format for beta versions used in Add-ons and WebExtensions
  • 4226 - "Review History" links for beta versions are useless
  • 4269 - "Incomplete" status for unlisted add-ons in Dev Hub homepage
  • 4282 - Click on incomplete status redirects to final step of submission
  • 4488 - Handle duplicate version better
  • 4491 - No source-code file available anywhere if added during new file submission
  • 4394 - "Completed" add-on is displayed as incomplete
  • 4302 - Misleading info while adding a second beta-listed version for an unlisted add-on
  • 4420 - Blocking submission for second listed version in 6 steps
  • 4427 - Beta add-on asking for resume after deleting first listed version
  • 4479 - 500 error page is loaded while unlisted version number is clicked from Admin Manage page
  • 4484 - Search in "All Unlisted Add-ons" is not working for add-on with mixed versions if first version is unlisted

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