| I18N Test Day | |
|---|---|
| |
| Date | 2026-09-07 to 2026-09-13 |
| Time | all day |
| Website | QA/Test Days |
| Matrix | #i18n:fedoraproject.org(other clients|?) |
| Mailing list | test |
If you come to this page 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, 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?[edit]
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[edit]
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Akira TAGOH (tagoh), Parag Nemade (paragan)
- Quality Assurance - Twinkle Pardeshi (twinkle28)
You can chat with us on Matrix. See the infobox on top of the page to learn where to join.
Prerequisite for Test Day[edit]
- A virtual machine or a bare metal machine
- One or more keyboards with different layouts
- An installation of Fedora 45 (any Edition or Spin with a graphical desktop). Make sure to fully update your system.
- If installing a fresh system, it's recommended to use the latest nightly image (alternative download locations: local mirror, master mirror).
- Make sure you have no important data on that system. Things might go wrong -- don't do this on your production machine!
- Alternatively, instead of using an installed system, you can run the tests directly from the Live image environment. Tips on using a live image are available at FedoraLiveCD.
How to test?[edit]
Visit the results 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 ➕ (plus) button for that test case.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Please follow the nomenclature of adding profile information for your testing while submitting test results:
- which variant? WS (Workstation) or SB (Silverblue) or Kinoite ?
- bare metal or VM?
- which language used?
- which arch used?
- if you upgraded from the previous release, please specify "upgrade".
Reporting bugs[edit]
Perhaps you've found an already-reported bug. Please look at:
Here are also some known issues that are relevant, but not present in the list above:
All new bugs should be reported into the upstream bug tracker (which differs per component/application), or Red Hat Bugzilla under the correct component/package.
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!
When filing the bug, it's very helpful to include:
- exact steps you've performed (and whether you can reproduce it again)
- screenshots or videos, if applicable
- system journal (log), which you can retrieve by
journalctl -b > journal.txt - all output in a terminal, if started from a terminal
- your system description
If you are unsure about exactly how to file the report or what other information to include, just ask us.
Please make sure to link to the bug when submitting your test result, thanks!
Fedora 45 Test Day Report[edit]
| No. of unique Languages | No. of participants | No. of New bugs filed | Total Bug list | Comments | |
|---|---|---|---|---|---|
| I18n | xx | xx | xx | package [RHBZ #xxxxxxx] |
