From Fedora Project Wiki

Fedora Test Week

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?[edit]

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

Who's available?[edit]

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

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[edit]

Testers need to have a Fedora 37 environment with the GNOME 43 RC included. There are several ways to set this up and this can include:

  • Using the test day iso image from above as a live desktop session without installing.
  • Updating an existing Fedora Workstation installation to latest Fedora 37, making sure latest packages from the updates-testing repository are installed and include the GNOME 43 RC version.

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

Files nightly builds[edit]

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

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[edit]

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

Run the tests[edit]

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[edit]

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[edit]

There are two places where bugs can be filed:

  1. Red Hat Bugzilla: this is Fedora's downstream issue tracker. Bugzilla should be used to report issues with packaging, or issues that need to be tracked as part of the release process. If you think that an issue might be a blocker bug, report it in Bugzilla.
  2. GNOME Gitlab: this is the GNOME project's upstream issue tracker. This should be used for any issue in a GNOME component, and is where GNOME issues get attention and get fixed. If you file a GNOME issue in Bugzilla 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 the test week chat channel in or #fedora-qa, and we will help you.

Test Results[edit]