Add-ons/QA/Testplan/NewHeader
From MozillaWiki
< Add-ons
Revision History
Date | Version | Author | Description |
---|---|---|---|
06/12/2017 | 1.0 | Carciu Victor | Created first draft |
Contents
Overview
A new design for the AMO header , on Desktop and Mobile
Purpose
Change the design of AMO header, following the new design specs
Entry Criteria
Current Status
- The feature is on -dev.
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?
- Test the new AMO header (for detail and landing pages) for UI and functionality issues
- Test on both AMO and Mobile
what's out of scope?
- None
Ownership
Product Manager: Jorge Villalobos; irc nick :jorgev
QA Manager: Krupa Raj; irc nick :krupa
QA Lead: Victor Carciu; irc nick :victorc
Add-ons QA: Valentina Virlics; irc nick :ValentinaV
Add-ons QA: Marius Santa; irc nick :Santa
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
- Release
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 | 25.05.2017 | |
Study PRD/mocks received | 09.06.2017 | |
QA - Test plan creation | 12.06.2017 | |
QA - Test cases preparation | 13.06.2017 | |
QA - Test cases execution | 13.06.2017 | |
Release Date | (Q3 - 2017) |
Testing Tools
Process | Tool |
---|---|
Test plan creation | Mozilla wiki |
Test case creation | TestRail - TBD |
Test case execution | TestRail - TBD |
Bugs management | Github |
References
* Mocks for AMO desktop - https://github.com/mozilla/addons-frontend/blob/master/assets/sketch%20files/AMO%20Desktop%20-%20Master.sketch * Tracker: 2436
Testcases
Test Areas
- Submission Tools/Reviewer Tools
Test suite
Full Test Suite TBD
Bug Work
- Feature implementation bug - 2436
Open bugs
Closed bugs
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