Confirmed users
114
edits
QA/Mozmill Test Automation/L10n Tests: Difference between revisions
Jump to navigation
Jump to search
QA/Mozmill Test Automation/L10n Tests (view source)
Revision as of 20:51, 24 April 2010
, 24 April 2010→Project details
(Excerpt) |
|||
| Line 30: | Line 30: | ||
=Project details= | =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== | ==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 addons window and Firefox main window | |||
==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. | |||
==Implementing a Test== | ==Implementing a Test== | ||
At first you should read through the [https://developer.mozilla.org/en/Mozmill_Tests#Writing_Mozmill_Tests test writing guidelines] to get familiar with the test creation. | |||
Once it is clear check the [http://hg.mozilla.org/qa/mozmill-tests/file/default/templates 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 [[QA/Mozmill_Test_Automation/Shared_Modules|shared module]] for localization needs to be created. | |||
To get new tests checked-in into our [http://hg.mozilla.org/qa/mozmill-tests/ mozmill-test repository] you will have to create a patch and go through the usual [https://developer.mozilla.org/en/Mozmill_Tests#Review_Process review cycle]. | |||
==Verifying the Test works== | ==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. | |||