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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Overview ==
== Overview ==
Having recently completed the redesign of AMO for Android, we’ve turned our attention to refreshing the desktop version.  
* Having recently completed the redesign of AMO for Android, we’ve turned our attention to refreshing the desktop version.
* The new homepage displays a subset of categories represented primarily though iconography… The density of information on an add-on detail page is more balanced now, with only essential information in clear view… and theme previews are bigger and screenshots more prominent.
* There’s a bit more color, too. In general much of the aesthetic was in need of a modernizing overhaul.


== Goals ==
== Goals ==
Modernizing the homepage and making it easier to find great add-ons
* Our main goal was to make browsing add-ons more intuitive and effortless. To that end, the new design presents content in a cleaner, more streamlined manner.
* Modernizing and making it easier to find great add-ons.


== Entry Criteria ==
== Entry Criteria ==
* QA has access to [mocks] . Any other info were found in bugs logged in GitHub
* QA has access to [https://github.com/mozilla/addons-frontend/blob/master/assets/sketch%20files/AMO%20Desktop%20-%20Master.sketch mocks]. Any other info were found in bugs logged in GitHub.


== Current status ==
== Current status ==
Line 57: Line 60:


== Channels ==
== Channels ==
* [Release]
* [https://archive.mozilla.org/pub/firefox/releases/ Release]
* [Nightly]
* [https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ Nightly]
* [Unbranded builds]
* [https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win64-add-on-devel/ Unbranded builds]


= Test Strategy =  
== Test Strategy ==  
== Test Execution Schedule ==
=== Test Execution Schedule ===
The following table identifies the anticipated testing period available for test execution.
The following table identifies the anticipated testing period available for test execution.
{| class="wikitable" style="width:60%"
{| class="wikitable" style="width:60%"
Line 84: Line 87:
|-
|-
| Release Date  
| Release Date  
|style="text-align:center;" | Release 57 ||  
|style="text-align:center;" | Firefox 57 ||  
|}
|}


Line 94: Line 97:
| Test plan creation || Mozilla wiki
| Test plan creation || Mozilla wiki
|-
|-
| Test case creation || [TestRail] / [Google docs]  
| Test case creation || [https://testrail.stage.mozaws.net/index.php?/suites/view/1297 TestRail]
|-
|-
| Bugs management || Github
| Bugs management || Github
Line 103: Line 106:
** This was the initial tracker, but individual issues for each added things where created in time
** 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]
* [https://github.com/mozilla/addons-frontend/blob/master/assets/sketch%20files/AMO%20Desktop%20-%20Master.sketch Redesign Files]


= Testcases =  
== Testcases ==  
=== Test Areas ===
=== Test Areas ===
* AMO Desktop Pages
* AMO Desktop Pages


=== Test suite ===
=== Test suite ===
Gdoc Test suite - tba
* [https://testrail.stage.mozaws.net/index.php?/suites/view/1297 Full Test Suite]
TestRail - tba


= Bug Work =
== Bug Work ==
=== Bug fix verification ===
=== Bug fix verification ===
* [https://github.com/mozilla/addons-server/labels/project%3A%20auto%20approval Open]
* [https://github.com/mozilla/addons-server/labels/project%3A%20auto%20approval Open]
Line 118: Line 121:


== Sign off ==
== Sign off ==
=== Criteria ===
=== Exit Criteria ===
Check list
Check list
* All test cases should be executed
* All test cases should be executed
* All blockers must be fixed and verified or have an agreed-upon timeline for being fixed
* All blockers must be fixed and verified or have an agreed-upon timeline for being fixed

Latest revision as of 13:42, 21 September 2017

Overview

  • Having recently completed the redesign of AMO for Android, we’ve turned our attention to refreshing the desktop version.
  • The new homepage displays a subset of categories represented primarily though iconography… The density of information on an add-on detail page is more balanced now, with only essential information in clear view… and theme previews are bigger and screenshots more prominent.
  • There’s a bit more color, too. In general much of the aesthetic was in need of a modernizing overhaul.

Goals

  • Our main goal was to make browsing add-ons more intuitive and effortless. To that end, the new design presents content in a cleaner, more streamlined manner.
  • Modernizing and making it easier to find great add-ons.

Entry Criteria

  • QA has access to mocks. Any other info were found in bugs logged in GitHub.

Current status

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 desktop homepage - header, content, footer
  • Install\Uninstall of Add-ons (webextensions, themes, lang packs, dictionaries, etc.)
  • Themes preview
  • Extensions/Themes details pages
  • Search - search suggestions, search results
  • Filter menu
  • Reviews and ratings - all reviews page
  • Extensions and Themes homepages and categories pages
  • Release notes
  • More themes/extensions by author_name
  • Pages using different languages (including RTL)
  • Collections
  • Statistics
  • User settings
  • Navigation
  • 404 States

what's out of scope?

  • Add-ons functionality

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

  • Windows
  • Mac OS

Servers

Channels

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 Firefox 57

Testing Tools

Process Tool
Test plan creation Mozilla wiki
Test case creation TestRail
Bugs management Github

References

Testcases

Test Areas

  • AMO Desktop Pages

Test suite

Bug Work

Bug fix verification

Sign off

Exit 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
Retrieved from "https://wiki.allizom.org/index.php?title=Add-ons/QA/Testplan/New_AMO_Desktop_Pages&oldid=1180892"