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.
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?[edit]
Today's installment of Fedora Test Day will focus on translations and keyboard layout support in Anaconda
Who's available[edit]
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - User:Petersen (juhp)
- Quality Assurance - IgorSoares (igorps), He Rui (rhe), A S Alam (Alam)
Prerequisite for Test Day[edit]
- 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?[edit]
Prepare Your System[edit]
- Tests requiring physical media (e.g. DVD or CD images) -- download F-14-Beta-TC1.
- Unless otherwise noted, you may use nightly Fedora 14 branch install images. Review for information on downloading and installing Branched.
- Optionally, you may download a non-destructive Fedora 14 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test Cases[edit]
Firstboot failed to run?
Please notice that F-14-Beta-TC1 has a known issue that firstboot is failed to run after installation. A workaround is to add a user manually on other ttys and turn back to gdm for login. Alternatively, you can use the live image available here.
Please notice that F-14-Beta-TC1 has a known issue that firstboot is failed to run after installation. A workaround is to add a user manually on other ttys and turn back to gdm for login. Alternatively, you can use the live image available here.
- QA:Testcase Arabic Language Install
- QA:Testcase Asian Language Install
- QA:Testcase Cyrillic Language Install
- QA:Testcase Non-English European Language Install
Test Results[edit]
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. 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 |    |
||
| Tian shixiong | Asian Language Install - Simplified Chinese | |
||
| David Ramsey | Asian Language Install - Japanese |  |
||
| A S Alam | Asian Language Install - Hindi | |||
| Krishnababu K | Asian Language Install - Telugu | |
| |
| Mingtao Niu | Asian Language Install - Simplified Chinese | |||
| He Rui | Asian Language Install - Simplified Chinese | |||
| Ani Peter | Asian Language Install - Malayalam | |
||
| Sweta Kothari | Asian Language Install - Gujarati | |
||
| Runa Bhattacharjee | Asian Language Install - Bengali (India) | |
||
| Giannis Konstantinidis | Non-English European Language Install - Greek | |
||
| Masami Ichikawa | Asian Language Install - Japanese | |
||
| Igor Soares | Non-English European Language Install - Brazilian Portuguese | |
||
| jiannis bonatakis | Greek Language Test | |||
| James Ni | Asian Language Install - Simplified Chinese | |||
| Epico | Non-English European Language Install - Germany | |
Basically ok, except when gdm login en_US keyboard layout is default as English is chosen. Note: when install, English language and Germany keyboard layout is chosen. | |
| Vpv | Non-English European Language Install | 635042 |
||
| ykopkova | Cyrillic Language Install - Russian | [2] [3] [4] |
Long comments[edit]
- ↑ Test passed. Will report component entries with additional details.
• During the installation on the first screen, there is the Fedora logo and 13? Is this correct?
• At the time zone screen, Tokyo 東京 is associated with Asia アシア as the country.
• Even though, I selected Japanese keyboard during the installation process, the US keyboard was listed as the default keyboard at the login screen.
• Even though, I selected Tokyo as my initial setup time zone, the default time zone is using Boston.
• During my sftp session, my session was not able to allow しながわ text. I had to do the *shinagawa*, the entry without the しながわ is listed as a blank line below.
• /etc/sysconfig/i18n LANG=ja-JP.UTF-8 correct!
• I like the new ibus. It is very sexy! Repeat I like the new ibus!!!
• Overall, enjoyed the Fedora 14 TC1!!! :)
- ↑ 1. Ignored the keyboard selection, as US keyboard is the default and ibus is used for input.
2. Correct timezone has been selected.
3. A number of messages are still in English
4. Encrytion (install time) & decryption (boot time) of block devices work as expected
5. Language packs correctly installed as per the default package selection
6. Installed system:
• Firstboot and GDM do not use the input method
• GDM accepts the password for the user created during firstboot
• Root password is accepted
• LANG=bn-IN.UTF-8 correctly reported in /etc/sysconfig/i18n
• Text editor and web-browsers function correctly with the language specific character
• Text input is uniform using ibus (tested with gedit, firefox, kwrite and OpenOffice writer)
• Nautilus seems to be using some translation from bn instead of bn-IN.
• Added to RHBZ #634548 for a similar problem in gdm • Some parts in anaconda are displayed in English and these have been traced to fuzzy strings in the F-14 branch. To be updated. • The nautilus string about 'receiving files over blue-tooth in the ~/Downloads folder' has been traced to a missing translation upstream in gnome-user-share. This has now been updated. Waiting to see if the next gnome-user-share build in koji fixes the issue. Else shall be filing a bug. - ↑ Terminal closes unexpectedly after using backspace or delete RHBZ #634739
•Some English texts appear during installation.Anaconda is not fully translated in Greek
- ↑ License Agreement isn't translated to Japanese. RHBZ #634680
• Keymap was selected collectly.
• Timezone was selected collectly.
• Passing encrypt password was no problem.
• Turning on/off Japanese input method worked as expected.
• Inputing Japanese was no problems
- ↑ Firstboot doesn't start after installation. AdamW writes in RHBZ #628241, that firstboot is broken in Beta TC 1, this will need more testing later.
