Test Day:2022-09-07 Fedora 37 GNOME 43 Final

Fedora Test Week
GNOME 43 RC
Date	2022-09-07 to 2022-09-14
Time	all day
Website	QA/Test Days
IRC	#fedora-workstation (webirc)
Mailing list	test

Can't make these dates?
If the test days have not happened yet, or have already finished, your testing is still valuable! The information on this page can still be used to test, and you can still file bugs and add results to the results section.

What to test?

This Fedora Test Week will focus on the GNOME 43 Release Candidate (RC).

Who's available?

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

• Development - Kalev Lember (kalev), Allan Day (aday)
• Quality Assurance - Adam Williamson (adamw), Sumantro Mukherjee (sumantrom), Kamil Páral (kparal), Thomas Garai (tcg121268), coremodule (coremodule).

Note that different from previous GNOME test days, this time we would like everybody to join the #fedora-workstation IRC channel instead of #fedora-test-day channel that we've used previously. Feel free to just come by and say hi. Everybody is welcome!

Test week setup

Testers need to have a Fedora 37 environment with the GNOME 43 RC included. To set this up:

1. Install Fedora 37 and update to the latest version
   • Install Fedora 37 using a nightly image, or by upgrading from a previous version
   • Once you have Fedora 37 installed, ensure that you have updates-testing repository enabled, and update to the latest version. Then check that your installed GNOME packages have the GNOME 43 RC version.
2. Install Fedora 37 using the dedicated GNOME 43 RC test day iso image.
3. Boot the test day iso image and use it as a live desktop session

Test installations can be on bare metal or in a virtual machine.

Files nightly builds

If you are doing exploratory Files testing, the Files nightly flatpak can be useful, since this allows running the new version of the file manager on an existing Fedora 36 installation. To install it, run the following in the terminal:

flatpak remote-add --if-not-exists gnome-nightly https://nightly.gnome.org/gnome-nightly.flatpakrepo

flatpak install org.gnome.NautilusDevel

Known bugs with this Flatpak compared with the packaged version:

• In the open with dialog, the full list of apps isn't available

These issues can be safely ignored when testing.

How to test?

Once you have a testing environment, set aside a block of time to carry out your tests.

Run the tests

Open the test week results page. Each column title links to a page describing a test to run through. Once you have run through a test, enter your results using the Enter result button. If you think that you have found an issue, create an issue report, and include the link to the report in the test result.

If possible, try to run through an entire category of tests (a category is an entire row in the table), rather than stopping part of the way through. You can choose to start with whichever category you prefer; try to focus on the categories that have had the least testing.

Exploratory testing

It is also useful to use Fedora 37 Workstation with GNOME 43 RC and see if you can find anything that's crashing or not working correctly.

When doing exploratory testing, take the time to focus on the new features in the upcoming release. These include:

• Redesigned system status menu
  • This can be accessed from the top bar, where the system status icons are
  • This feature is best tested using a bare metal installation, due its high level of hardware integration
  • Things to focus on:
    • Do each of the toggle buttons work as expected?
    • Can you perform your usual connectivity tasks: connect to Wi-Fi, Bluetooth, VPN, Bluetooth tethers, USB tethers.
• Files (nautilus) GTK 4 port
  • The default file manager has been ported to GTK 4 for GNOME 43. This is primarily a technical change, but there have been a large number of small design changes also.
  • This feature is best tested through ongoing dog fooding: can you use the new Files version as your daily file manager? Does it perform well with the files and folders that you typically interact with?
  • In addition to testing using the Fedora 37 package, it is also possible to test using the nightly Flatpak (see above).
• Initial setup GTK 4 port
• Software sources dropdown
  • This dropdown is now located below the install/open/remove button on each app page
  • To test this, try adding a few different types of app repository, and see how it looks and behaves for different applications

Reporting bugs

We have two separate places to file bugs. First, downstream in Fedora bug tracker. This is mostly useful for issues with packaging and for issues that need tracking downstream (blocker bugs for F37): Red Hat Bugzilla.

Second, there's upstream GNOME Gitlab that's useful for issues that are likely not Fedora-specific. If you file an issue downstream that looks like it needs a code fix, please file it upstream as well, to make sure all relevant people get notified of the issue.

If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.