| Fedora Test Days | |
|---|---|
| |
| L10n/i18n Installation | |
| Date | 2011-08-31 |
| Time | all day |
| Website | QA/Fedora_16_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 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 internationalization support in Anaconda
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion.
- Development -
- Quality Assurance - IgorSoares (igorps), Rhe (rhe)
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
- Tests requiring physical media (e.g. DVD or CD images) -- [link to F-16-Alpha].
- Unless otherwise noted, you may use nightly Fedora 16 branch install images. Review for information on downloading and installing Branched.
- Optionally, you may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found [ here].
Test Cases
Since GDM currently has no language or session choosers, you need login to the system and select system->system settings, then choose the language either in User Accounts or Region and Language.
- QA:Testcase Arabic Language Install
- QA:Testcase Asian Language Install
- QA:Testcase Cyrillic Language Install
- QA:Testcase Non-English European Language Install
- QA:Testcase i18n default fonts
Nice to test
Bugs you might hit or additional situations that are nice to test:
Test Results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component anaconda. 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 the test case you followed. Use the result template to enter your results in the third column, as shown in the example result line.
| User | Test Description | Result | References |
|---|---|---|---|
| Sample User | <AREA> Language Install - <LANG> |   |
