31
edits
Add-ons/QA/Testplan/Webextensions Language Packs: Difference between revisions
Jump to navigation
Jump to search
Add-ons/QA/Testplan/Webextensions Language Packs (view source)
Revision as of 12:56, 2 October 2017
, 2 October 2017→Overview
| Line 9: | Line 9: | ||
= Overview = | = Overview = | ||
* A language pack is an | * A language pack is an add-on that changes the language of the user interface in a Mozilla application (Firefox, Thunderbird, SeaMonkey, etc.). | ||
* | * Switching to the new language pack formats will allow us to remove language packs from requiring the old add-ons ecosystem, they will be safer(no direct access to chrome registry) and will enable L10nRegistry (bug 1333980) which is required for transitioning to the new l10n API (bug 1365426). | ||
== Purpose == | == Purpose == | ||
* | * This document's purpose is to detail the test approach to the Language Packs Webextensions packaging, including Entry/Exit criteria, Scope for testing, links to testcases etc | ||
=== Entry Criteria === | === Entry Criteria === | ||
| Line 30: | Line 29: | ||
== Scope == | == Scope == | ||
This section describes what parts of the feature will be tested and what parts won't be. | |||
===what's in scope?=== | ===what's in scope?=== | ||
* Lang Packs validation - recognize the special kind of extension based on some entry in manifest.json | * Lang Packs validation - recognize the special kind of extension based on some entry in manifest.json | ||