Add-ons/QA/Testplan/New AMO Desktop Pages
From MozillaWiki
< Add-ons
Contents
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
- The feature is in -dev: https://addons-dev.allizom.org/en-US/firefox/.
- 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 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
- Stage: https://addons.allizom.org/en-US/
- Dev: https://addons-dev.allizom.org/en-US/
- Production: https://addons.mozilla.org/en-US/
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
- 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
- New AMO Desktop Scoping
- Redesign Files
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
