Add-ons/QA/Testplan/New AMO Desktop Pages: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 98: Line 98:


= References =
= References =
* Tracker - https://github.com/mozilla/addons-frontend/issues/2296
* Tracker - https://github.com/mozilla/addons-frontend/issues/2296  
** This was the initial tracker, but individual issues for each added things where created in time
* [https://docs.google.com/document/d/1cJ1k8HsAb6taauvJMDLOiYMa1McfUXNgEtax3hoToPc/edit?pli=1#heading=h.9q1woklhtvbx New AMO Desktop Scoping]
* [https://docs.google.com/document/d/1cJ1k8HsAb6taauvJMDLOiYMa1McfUXNgEtax3hoToPc/edit?pli=1#heading=h.9q1woklhtvbx New AMO Desktop Scoping]



Revision as of 12:40, 21 September 2017

Overview

Having recently completed the redesign of AMO for Android, we’ve turned our attention to refreshing the desktop version.

Goals

Modernizing the homepage and making it easier to find great add-ons

Entry Criteria

Current status

  • The feature is in -dev.
  • Still under development

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
  • Install\Uninstall of Add-ons and Themes
  • Search for Add-ons and Themes. Sorting the search results. Search suggestions.
  • Add-on and Themes reviews and ratings
  • Add-ons and Themes categories
  • AMO mobile pages in different languages and RTL view
  • Collections - not sure if this will be implemented but is present on mocks
  • Versions availability in AMO mobile public pages
  • Themes preview
  • User settings
  • 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: Valentina Virlics; irc nick :ValentinaV


Requirements for testing

Environments

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 Date
Start project 21.04.2017
Study PRD/mocks received 21.04.2017
QA - Test plan creation 01.07.2017
QA - Test cases preparation 01.08.2017
QA - Test cases execution 01.08.2017
Release Date Release 57

Testing Tools

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

References

Testcases

Test Areas

  • AMO Desktop

Test suite

Gdoc Test suite - 
TestRail - 

Bug Work

  • All Feature bugs:
    • [Open]
    • [Closed]

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