[F45 test days] I18n #924

Open
opened 2026-07-30 07:13:26 +00:00 by kparal · 17 comments
Owner

Similar to previous releases, @pnemade will want to see test days for i18n. Let's use this ticket to set it up.

Similar to previous releases, @pnemade will want to see test days for i18n. Let's use this ticket to set it up.
kparal added this to the Fedora 45 milestone 2026-07-30 07:15:47 +00:00
kparal self-assigned this 2026-08-06 10:53:45 +00:00
Author
Owner

Hi @pnemade , do you know the desired dates already? I can then prepare some of the skeleton pages to fill out.

Hi @pnemade , do you know the desired dates already? I can then prepare some of the skeleton pages to fill out.
I have setup the test week event now. https://fedoraproject.org/wiki/Test_Day:2026-09-07_I18N_Test_Day https://testdays.fedoraproject.org/testday/23
Author
Owner

Awesome, thanks a lot. I'll polish it a bit and work on the remaining bits (calendar, etc). (But I'm away next week, so after that).

Awesome, thanks a lot. I'll polish it a bit and work on the remaining bits (calendar, etc). (But I'm away next week, so after that).
kparal added the due date 2026-09-03 2026-08-19 09:02:03 +00:00
Author
Owner

I've updated the wiki page, the test results page, added a fedocal event, and scheduled an announce email to test-announce and to discussion (currently hidden, will become listed later).

Please announce the event in further appropriate places, once we're closer to the date, thanks!

I think we're ready. Please speak up if something else needs tweaking, thanks.

I've updated the wiki page, the test results page, added a fedocal event, and scheduled an announce email to test-announce and to [discussion](https://discussion.fedoraproject.org/t/test-days-f45-internationalization/199875) (currently hidden, will become listed later). Please announce the event in further appropriate places, once we're closer to the date, thanks! I think we're ready. Please speak up if something else needs tweaking, thanks.

Looks good to me. Thank you for your help.

Looks good to me. Thank you for your help.
Author
Owner

@bookwar wrote to the #quality Matrix channel:

I've read that there is going to be Internationalization test day soon https://testdays.fedoraproject.org/testday/23 From the set of test cases it seems to be focused on the running environment. Do you think we can add a test case for the Installer into it, specifically focused on the installation in different languages?
We don't want to steal the focus completely, but we also have quite a lot of issues reported to the installer last minute because of the bugs in keyboard layouts/language configuration. So it seems to be ontopic to ask people to try the Installer WebUI in different languages as a part of the test day.

We can discuss there, I'm just mentioning it here so that we don't forget about it.

@bookwar wrote to the #quality Matrix channel: > I've read that there is going to be Internationalization test day soon https://testdays.fedoraproject.org/testday/23 From the set of test cases it seems to be focused on the running environment. Do you think we can add a test case for the Installer into it, specifically focused on the installation in different languages? We don't want to steal the focus completely, but we also have quite a lot of issues reported to the installer last minute because of the bugs in keyboard layouts/language configuration. So it seems to be ontopic to ask people to try the Installer WebUI in different languages as a part of the test day. We can discuss there, I'm just mentioning it here so that we don't forget about it.
I added simple testcase https://fedoraproject.org/wiki/QA:Testcase_i18n_Anaconda_Installer

@pnemade wrote in #924 (comment):

I added simple testcase https://fedoraproject.org/wiki/QA:Testcase_i18n_Anaconda_Installer

Thank you for adding the testcase.

We have one important (and rather fragile according to the past experience) scenario, which is disk encryption password and keyboard selection. Do you think we could add a test case that explicitly requires using the disk encryption and checks
that the disk is successfully unlocked after installed system reboot?

If there would be capacity for only single installer test, I'd prefer ro replace the simple test case with the encrypted disk one.

@pnemade wrote in https://forge.fedoraproject.org/quality/tickets/issues/924#issuecomment-1351878: > I added simple testcase https://fedoraproject.org/wiki/QA:Testcase_i18n_Anaconda_Installer Thank you for adding the testcase. We have one important (and rather fragile according to the past experience) scenario, which is disk encryption password and keyboard selection. Do you think we could add a test case that explicitly requires using the disk encryption and checks that the disk is successfully unlocked after installed system reboot? If there would be capacity for only single installer test, I'd prefer ro replace the simple test case with the encrypted disk one.
Author
Owner

We have these test cases available in our release validation matrices:

All of them use an encrypted disk. We can add any of these to the test day, if you like (or write a custom one).

We have these test cases available in our release validation matrices: * https://fedoraproject.org/wiki/QA:Testcase_Arabic_Language_Install * https://fedoraproject.org/wiki/QA:Testcase_Asian_Language_Install * https://fedoraproject.org/wiki/QA:Testcase_Cyrillic_Language_Install * https://fedoraproject.org/wiki/QA:Testcase_Non-English_European_Language_Install All of them use an encrypted disk. We can add any of these to the test day, if you like (or write a custom one).

These are already great, well-defined test cases.

I can see they are part of final release criteria. Do you think it would make sense make them part of the test day then? For example to have bugs discovered earlier? I think even this would be very valuable for Anaconda team.

Originally we were thinking about (exploratory) free of choice of 2nd language/keyboard test, hoping to have testers explorative / diverse enough to look for issues (perhaps naive, not sure if it would work like this though).

Maybe we could use the intersection of the 4 tests, with language of choice (or suggestion to pick a language that could break the case). I guess we want to keep esp. the point 5. (for #681250) to prevent reporting known issue.

Also we care only about testing of WebUI (not GtkUI) in scope of the test days.

.. So I think having the 4 tests + 1 test with exploratory choice of language, focused specifically on WebUI would be ideal in case of infinite testers force (yes Anaconda team should participate on the test days), but here I'd also ask for your guidance or recommendations.

These are already great, well-defined test cases. I can see they are part of final release criteria. Do you think it would make sense make them part of the test day then? For example to have bugs discovered earlier? I think even this would be very valuable for Anaconda team. Originally we were thinking about (exploratory) free of choice of 2nd language/keyboard test, hoping to have testers explorative / diverse enough to look for issues (perhaps naive, not sure if it would work like this though). Maybe we could use the intersection of the 4 tests, with language of choice (or suggestion to pick a language that could break the case). I guess we want to keep esp. the point 5. (for #681250) to prevent reporting known issue. Also we care only about testing of WebUI (not GtkUI) in scope of the test days. .. So I think having the 4 tests + 1 test with exploratory choice of language, focused specifically on WebUI would be ideal in case of infinite testers force (yes Anaconda team should participate on the test days), but here I'd also ask for your guidance or recommendations.
Owner

We do have fairly good automated test coverage for those test cases also. We have Asian, Cyrillic and European for both webUI and gtkUI; Arabic and Turkish we do for gtkUI only ATM (I should add those to webUI). So we do catch issues quite early usually.

Of course, having people run them interactively at test days is also good, they may well do something a bit different from openQA and catch issues it missed.

We do have fairly good automated test coverage for those test cases also. We have Asian, Cyrillic and European for both webUI and gtkUI; Arabic and Turkish we do for gtkUI only ATM (I should add those to webUI). So we do catch issues quite early usually. Of course, having people run them interactively at test days is also good, they may well do something a bit different from openQA and catch issues it missed.

@kparal wrote in #924 (comment):

We have these test cases available in our release validation matrices:

* https://fedoraproject.org/wiki/QA:Testcase_Arabic_Language_Install

* https://fedoraproject.org/wiki/QA:Testcase_Asian_Language_Install

* https://fedoraproject.org/wiki/QA:Testcase_Cyrillic_Language_Install

* https://fedoraproject.org/wiki/QA:Testcase_Non-English_European_Language_Install

All of them use an encrypted disk. We can add any of these to the test day, if you like (or write a custom one).

I think if we need to add those test cases then it will be good to have one unique test case that covers all different languages.

@kparal wrote in https://forge.fedoraproject.org/quality/tickets/issues/924#issuecomment-1351974: > We have these test cases available in our release validation matrices: > > * https://fedoraproject.org/wiki/QA:Testcase_Arabic_Language_Install > > * https://fedoraproject.org/wiki/QA:Testcase_Asian_Language_Install > > * https://fedoraproject.org/wiki/QA:Testcase_Cyrillic_Language_Install > > * https://fedoraproject.org/wiki/QA:Testcase_Non-English_European_Language_Install > > > All of them use an encrypted disk. We can add any of these to the test day, if you like (or write a custom one). I think if we need to add those test cases then it will be good to have one unique test case that covers all different languages.
Author
Owner

@pnemade Ok, so I re-used your https://fedoraproject.org/wiki/QA:Testcase_i18n_Anaconda_Installer and linked to the 4 specific test cases inside of it. I also put it into its own category in https://testdays.fedoraproject.org/testday/23 .

Does that work for both you @pnemade @rvykydal ? Feel free to edit the test case as much as you like to fit your needs. Do we need a second one for something specific?

@pnemade Ok, so I re-used your https://fedoraproject.org/wiki/QA:Testcase_i18n_Anaconda_Installer and linked to the 4 specific test cases inside of it. I also put it into its own category in https://testdays.fedoraproject.org/testday/23 . Does that work for both you @pnemade @rvykydal ? Feel free to edit the test case as much as you like to fit your needs. Do we need a second one for something specific?

@kparal Thank you for your help. Looks good to me.

@kparal Thank you for your help. Looks good to me.

@kparal thank you, to me it looks great, I think this is what we need.

@kparal thank you, to me it looks great, I think this is what we need.

Also, we have some known issues in current compose:

https://bugzilla.redhat.com/show_bug.cgi?id=2510055 (a race condition not really easy to hit AFAIK)
https://bugzilla.redhat.com/show_bug.cgi?id=2508253

The former has already a fix merged (but not released): https://github.com/rhinstaller/anaconda/pull/7273

I am mentioning it in case it would make sense advertise them for the testers (AFAIK there are only blocker / exception bugs mentioned)

Also, we have some known issues in current compose: https://bugzilla.redhat.com/show_bug.cgi?id=2510055 (a race condition not really easy to hit AFAIK) https://bugzilla.redhat.com/show_bug.cgi?id=2508253 The former has already a fix merged (but not released): https://github.com/rhinstaller/anaconda/pull/7273 I am mentioning it in case it would make sense advertise them for the testers (AFAIK there are only blocker / exception bugs mentioned)
Author
Owner

The first one is already present in the blockerbugs app view, I added the second one here:
https://fedoraproject.org/wiki/Test_Day:2026-09-07_I18N_Test_Day#Reporting_bugs

Anyone, feel free to extend that section.

The first one is already present in the blockerbugs app view, I added the second one here: https://fedoraproject.org/wiki/Test_Day:2026-09-07_I18N_Test_Day#Reporting_bugs Anyone, feel free to extend that section.
Sign in to join this conversation.
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-09-03

Reference
quality/tickets#924
No description provided.