| 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, Rawhide (tips on installing Rawhide below), or a nightly live 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 or Beta TC1 images.
Run the tests
Visit the result page and click on the links to see the tests that need to be run. Follow the instructions there, then enter your results as explained below.
Live image
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test Cases
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.
Test Results
Please make sure if you have lang=xx in your hardware profile to indicate what language you are testing with so that there are no fields in the TestdayApp to let us know your testing language.
If you have problems with any of the tests, report a bug to Bugzilla with i18n keyword. For instance file a bug report against the component firefox if you have problems testing the Firefox Web Browser. adding i18n keyword to Keywords field in bugzilla is important part in order to keep it on track. 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 separate pages by testing categories below.
| User | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |