From Fedora Project Wiki
DATE TIME WHERE
2010-09-16 All Day #fedora-test-day (webirc)
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule - which should be linked at QA/Test_Days - and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on translations and keyboard layout support in Anaconda

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

  • One or more keyboards with different layouts.
  • Bare metal or virtual machine.
  • Usb key, a virtualized guest or a burned CD/DVD with the test image

How to test?

Prepare Your System

Test Cases

Test Results

Specific L10N bugs like typos and translation mistakes should be directly reported to the local translation team mailing list or a bug report should be filed at Bugzilla against the related language. General bugs that affect all languages like strings not marked for translation, downstream patching that breaks translations and input method issues should be filed against the related package. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, if your system worked correctly, simply enter the word {{result|pass}}. If you had trouble, enter the word {{result|warn}}<ref>xxx</ref> or {{result|fail|bug No}}, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.

User Test Description Result References
Sample User Asian Language Install - Chinese
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Tian shixiong Asian Language Install - Simplified Chinese
Warning warn
[1]
  1. Test pass, but also encountered RHBZ #634385
David Ramsey Asian Language Install - Japanese
Inprogress inprogress
A S Alam Asian Language Install - Hindi
Inprogress inprogress
Krishnababu K Asian Language Install - Telugu
Inprogress inprogress
Mingtao Niu Asian Language Install - Simplified Chinese
Pass pass newgle1
He Rui Asian Language Install - Simplified Chinese
Warning warn rhe [1] [2] [3]
  1. RHBZ #634475
  2. RHBZ #634484
  3. RHBZ #634486
Ani Peter Asian Language Install - Malayalam
Inprogress inprogress
none