From Fedora Project Wiki

Associated release criterion
This test case is associated with the Fedora_42_Final_Release_Criteria#installer-translations release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Associated release criterion
This test case is associated with the Fedora_42_Final_Release_Criteria#keyboard-layout-configuration release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case tests installation using a Cyrillic language. Testing also includes verifying a good keymap is selected during installation and used for all purposes in the installed system.

Testing with just a US keyboard?
You do not need different physical keyboard layouts to complete this test. Logical keyboard layouts are applied independent of physical keyboard hardware; if you test with a US-marked keyboard but pick, e.g., the French keyboard layout, the key marked 'Q' will now produce the character 'A'. Of course, it helps to know how the layout you test with actually looks.

Setup

  1. Prepare a test system with a working, supported storage device of sufficient size for a Fedora install, and a Fedora installation medium that uses the GTK-based installer. Do not use Fedora Workstation live on Fedora 41+, as that uses the webui-based installer.

How to test

  1. Boot the installer using any available means.
  2. On the Welcome screen, choose a Cyrillic language, such as Russian, and click Continue.
  3. Check the keyboard layout(s) shown under KEYBOARD on the main screen are appropriate for the language.
  4. Click INSTALLATION DESTINATION, and check Encrypt my data. Leave Automatically configure partitioning. selected. Click Done.
  5. Enter an encryption passphrase using characters that are placed differently on the keyboard layout in use than they are on the US keyboard layout. If using a configuration where it is customary to switch between a 'native' layout and the US layout for entering ASCII characters, use only characters from the first layout (usually US): due to #681250, you cannot use characters from the second layout when entering the passphrase to decrypt the device.
  6. If necessary, free up space for the installation via the Reclaim space screen.
  7. Click Begin Installation.
  8. While installation proceeds, create a user account, using characters that are placed differently on the keyboard layout in use than they are on the US keyboard layout in the username and/or password. If using a configuration where it is customary to switch between a 'native' layout and the US layout for entering ASCII characters, use at least some characters from the 'native' layout.
  9. Boot the installed system. When prompted, enter the encryption passphrase.
  10. Log in to the booted system using the user you created.
  11. Check the keyboard layout in use in the user's session.

Expected Results

  1. The correct character set is displayed in the language selection step.
  2. An appropriate keymap is selected based on the language and location selected.
  3. Text input using the selected keymap works as expected.
  4. Text for which a translation is available is shown translated.
  5. The encryption passphrase entered during installation works on boot of the installed system (i.e. the correct keymap is used when decrypting encrypted partitions).
  6. The username and password entered during installation work to log in to the installed system (i.e. the correct keymap is used when logging in).
  7. The correct keymap is used as the default when logged in to the system.
  8. If using a configuration where it is customary to switch between a 'native' layout and the US layout for entering ASCII characters, switching works at login and when logged in (it is a known limitation that it does not working at passphrase entry).