QA/Mozmill Test Automation/L10n Tests: Difference between revisions
No edit summary |
|||
| Line 11: | Line 11: | ||
|- valign="top" | |- valign="top" | ||
| '''Dates:''' | | '''Dates:''' | ||
| shared-modules - | | shared-modules - reviews ongoing | ||
|- valign="top" | |- valign="top" | ||
| | | | ||
| Line 41: | Line 41: | ||
==Status== | ==Status== | ||
The status of L10n Mozmill tests as of | The status of L10n Mozmill tests as of October, 14th 2010: | ||
* | * DomUtilsAPI (including DOMWalker) and L10nAPI: reviews on going | ||
* Both tests for the preferences window are nearly finished and already finding bugs in every tested locale. Holding on review-requests until the shared modules don't get positive reviews | |||
* Both tests for the preferences window are nearly finished and already finding bugs in every tested locale | |||
* The tests for the software update window are on hold, as this window is being rewritten | * The tests for the software update window are on hold, as this window is being rewritten | ||
==Filing a Bug== | ==Filing a Bug== | ||
We have prepared a [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&cc=akalla%40aviary.pl&comment=&component=Mozmill&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&dependson=&description=&flag_type-37=X&flag_type-4=X&flag_type-607=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Testing&qa_contact=mozmill%40testing.bugs&rep_platform=All&short_desc=%5Bmozmill%5D%20%5BL10n-tests%5D%20&status_whiteboard=&target_milestone=---&version=unspecified template] which makes the creation of a bug as easy as possible. | We have prepared a [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=nobody%40mozilla.org&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&cc=akalla%40aviary.pl&comment=&component=Mozmill&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&dependson=&description=&flag_type-37=X&flag_type-4=X&flag_type-607=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=Testing&qa_contact=mozmill%40testing.bugs&rep_platform=All&short_desc=%5Bmozmill%5D%20%5BL10n-tests%5D%20&status_whiteboard=&target_milestone=---&version=unspecified template] which makes the creation of a bug as easy as possible. | ||
Revision as of 17:36, 14 October 2010
Overview
| Lead: | Adrian Kalla |
| Co-workers: | Henrik Skupin |
| Dates: | shared-modules - reviews ongoing |
| tests - after the shared-modules get a positive review | |
| Status: | pre-review |
| 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.
Status
The status of L10n Mozmill tests as of October, 14th 2010:
- DomUtilsAPI (including DOMWalker) and L10nAPI: reviews on going
- Both tests for the preferences window are nearly finished and already finding bugs in every tested locale. Holding on review-requests until the shared modules don't get positive reviews
- The tests for the software update window are on hold, as this window is being rewritten
Filing a Bug
We have prepared a template which makes the creation of a bug as easy as possible.