Add-ons/QA/Testplan/Webextensions Language Packs: Difference between revisions
< Add-ons
Jump to navigation
Jump to search
ValentinaP (talk | contribs) |
ValentinaP (talk | contribs) |
||
Line 9: | Line 9: | ||
= Overview = | = Overview = | ||
* | * A language pack is an extension (add-on) that changes the language of the user interface in a Mozilla application (Firefox, Thunderbird, SeaMonkey, etc.). | ||
* For example, if you have an English version of Thunderbird, then the first button on Thunderbird's toolbar has the label "Get Mail" and the tooltip "Get new messages". But if you install the French language pack and switch the user interface to French, then the first button on Thunderbird's toolbar has the new label "Relever" and the tooltip "Relever les nouveaux messages". | |||
* | |||
== Purpose == | == Purpose == | ||
* | * Together with Firefox 57 we must find ourselves using entirely webextensions. | ||
* Being able to use Language Packs after changes land. | |||
=== Entry Criteria === | === Entry Criteria === |
Revision as of 12:36, 14 September 2017
Revision History
Date | Version | Author | Description |
---|---|---|---|
09/14/2017 | 1.0 | Valentina Virlics | Created first draft |
Overview
- A language pack is an extension (add-on) that changes the language of the user interface in a Mozilla application (Firefox, Thunderbird, SeaMonkey, etc.).
- For example, if you have an English version of Thunderbird, then the first button on Thunderbird's toolbar has the label "Get Mail" and the tooltip "Get new messages". But if you install the French language pack and switch the user interface to French, then the first button on Thunderbird's toolbar has the new label "Relever" and the tooltip "Relever les nouveaux messages".
Purpose
- Together with Firefox 57 we must find ourselves using entirely webextensions.
- Being able to use Language Packs after changes land.
Entry Criteria
- QA has access to PRD and some mocks (found in bugs)
- The feature has landed in -dev
Current Status
- The feature is in -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?
what's out of scope?
- Extensions functionality
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
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 | 17.05.2017 | |
Study PRD/mocks received | ||
QA - Test plan creation | 14.09.2017 | |
QA - Test cases preparation | ||
QA - Test cases execution | ||
Release Date |
Testing Tools
Process | Tool |
---|---|
Test plan creation | Mozilla wiki |
Test case creation | TestRail / Google docs |
Test case execution | TestRail |
Bugs management | Github |
References
* PRD - * Tracker: 6297
Testcases
Test Areas
- Submission/Approvals/Installation of Webextensions Lang Packs
Test suite
Full Test suite
Bug Work
- Tracking bug - 6297
Bug fix verification
Logged 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