Confirmed users
114
edits
QA/Mozmill Test Automation/L10n Tests: Difference between revisions
Jump to navigation
Jump to search
m
QA/Mozmill Test Automation/L10n Tests (view source)
Revision as of 20:53, 24 April 2010
, 24 April 2010→Project details
| Line 36: | Line 36: | ||
An important goal is also to first create a shared L10n module for the above tests. | An important goal is also to first create a shared L10n module for the above tests. | ||
==Identifying L10n Test Candidates== | ==Identifying L10n Test Candidates== | ||
| Line 42: | Line 41: | ||
* 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 addons window and Firefox main window | * 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. | 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== | ||
| Line 56: | Line 53: | ||
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]. | 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. | 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. | ||