|Fedora Test Days|
|Mail • Subscribe • Archives|
- 1 What to test?
- 2 Who's available
- 3 Prerequisite for Test Day
- 4 How to test?
- 5 Reporting bugs
- 6 Test Results
- 7 Fedora 24 Test Day Report
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.
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.
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.
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.
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.
Fedora 24 changes
|User||Profile||glibc locale subpackaging||langpacks packages||ibus fbterm||References|
Input(language specific) tests
|User||Profile||ibus-bogo (Vietnamese)||ibus-hangul (Hangul)||ibus-kkc (Japanese)||ibus-libpinyin (Simplified Chinese)||ibus-libzhuyin (Traditional Chinese)||ibus-m17n (Indic)||ibus-cangjie (Traditional Chinese)||ibus-cangjie (Traditional Chinese)||References|
|User||Profile||fonts-tweak-tool||dnf-langpacks plugin (obsoleted by langpacks packages)||References|
Fedora 24 Test Day Report
|No.of Applications Tested||No.of Languages||No.of bugs filed||No.of participants||Bug list|
|I18n||11||6||3||10||dnf-plugins-core [RHBZ #1326095]
glibc [RHBZ #1326470]
lohit-marathi-fonts RHBZ #1325493]