| Fedora Test Days | |
|---|---|
| |
| I18N | |
| Date | 2016-04-12 |
| Time | all day |
| Website | QA/Fedora_24_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 Internationalization a.k.a. i18n around Desktops including their applications. this aims to ensure if i18n support works enough on them.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Akira TAGOH (tagoh_), Pravin Satpute (pravins)
- Quality Assurance - Adam Williamson (adamwill)
Prerequisite for Test Day
- One or more keyboards with different layouts
- An updated Fedora 24 pre-release, or a Fedora 24 nightly image
How to test?
Update your machine
If you test with an installed system, make sure you have all the current updates installed, using the update manager, especially if you use the Alpha images.
Live image
Instead of testing on an installed system, you may download a Fedora 24 nightly live image for your architecture. Tips on using a live image are available at FedoraLiveCD. The latest live image links can be found here: please make sure to get a Fedora 24 nightly, not Rawhide.
Run the tests
Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
For the glibc locale subpackaging test, follow the How To Test page.
Reporting bugs
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla for the appropriate component. 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.
Test Results
Please enter your results on the result page. The results will be transferred here after the Test Day is finished.
Please make sure you have lang=xx in your hardware profile to indicate what language you are testing with, as there are no fields in the test day results app to let us know your testing language.