QA/Mozmill Test Automation/L10n Tests: Difference between revisions
| Line 40: | Line 40: | ||
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.: | 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 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 | * in case of doubled access keys the probably most important windows will be the Preferences window and Firefox main window | ||
==Filing a Bug== | ==Filing a Bug== | ||
Revision as of 20:54, 24 April 2010
Overview
| Lead: | Adrian Kalla |
| QA: | Henrik Skupin |
| Dates: | Q3/2010 |
| Status: | Planning |
| Repository Location: | http://hg.mozilla.org/qa/mozmill-tests/ |
| Tracking Bug: | - |
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
Filing a Bug
We have prepared a template which makes the creation of a bug as easy as possible.
Implementing a Test
At first you should read through the test writing guidelines to get familiar with the test creation.
Once it is clear check the available templates which have been prepared for a new test. Copy and paste the content into a new file to get the raw structure for your test. Finally fill in your details in the license plate.
Before implementing the tests itself, a shared module for localization needs to be created.
To get new tests checked-in into our mozmill-test repository you will have to create a patch and go through the usual review cycle.
Verifying the Test works
Once the patch has been checked-in, the bug will be marked as fixed. We will wait for the next test-run on our machine in the QA lab. If no problems or regressions appear we are fine and you did a great job. Otherwise we have to back-out the patch and go back to the investigation phase and check why the test fails.