QA/Mozmill Test Automation/L10n Tests: Difference between revisions
m (→Project details: unneeded stuff) |
|||
| Line 11: | Line 11: | ||
|- valign="top" | |- valign="top" | ||
| '''Dates:''' | | '''Dates:''' | ||
| shared-modules - | | shared-modules - September, 30th 2010 | ||
|- valign="top" | |- valign="top" | ||
| | | | ||
| tests - | | tests - October, 8th 2010 | ||
|- valign="top" | |- valign="top" | ||
| '''Status:''' | | '''Status:''' | ||
| Line 20: | Line 20: | ||
|- valign="top" | |- valign="top" | ||
| '''Repository Location:''' | | '''Repository Location:''' | ||
| [http://hg.mozilla.org/qa/mozmill-tests/file/default/firefox/ | | [http://hg.mozilla.org/qa/mozmill-tests/file/default/firefox/testLocalization L10n tests] | ||
|- valign="top" | |- valign="top" | ||
| '''Tracking Bug:''' | | '''Tracking Bug:''' | ||
Revision as of 17:24, 28 September 2010
Overview
| Lead: | Adrian Kalla |
| Co-workers: | Henrik Skupin |
| Dates: | shared-modules - September, 30th 2010 |
| tests - October, 8th 2010 | |
| Status: | Planning |
| Repository Location: | L10n tests |
| Tracking Bug: | Bug 562084 |
Excerpt
Mozmill L10n Tests will allow us to check for common problems found in localized Firefox builds, which are often hard to find for the localizers themselves. Doing L10n tests on all localized builds manually is extremely time consuming, so this will allow us to automatically test things which cannot be tested with compare-locales. It is planned to link in the future to the results of that tests on the L10n Dashboard.
This project aims to create the Mozmill L10n Tests and a shared L10n module.
Project details
The project aims to focus mainly on two types of localization tests:
- testing for cut off text in windows in cases where the localized text was too long
- testing for not properly working access keys (usually doubled or tripled access keys)
Such tests cannot be performed with tools working just with source files (e.g.: compare-locales), they have to be done with Mozmill.
An important goal is also to first create a shared L10n module for the above tests.
Identifying L10n Test Candidates
As writing tests for every window or menu to test for cut off text or double access keys won't be possible, because there are simply too many of them, we will have to make a priority list and start implementing the most important first, e.g.:
- in case of cut off text the probably most important windows will be the Upgrade and Update windows
- in case of doubled access keys the probably most important windows will be the Preferences window and Firefox main window (main menu & context menu)
Filing a Bug
We have prepared a template which makes the creation of a bug as easy as possible.