| 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 |
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).
Prerequisites for Test Day
Testers must have a Fedora 37 environment with the GNOME 43 RC included. This can include:
- An existing Fedora Workstation 37 installation with the test updates repositories enabled, and updated to the latest version. If using this option, make sure to check that installed GNOME packages have the RC version before running the tests.
- A new Y37 installation using the [ nightly ISO image with GNOME 43 RC].
Testing can be accomplished with a live image, bare metal installations, or virtual machine installations. Note that, in some cases, the type of installation may affect what can be tested.
Files Nightly Builds
The Files nightly flatpak can be a useful way to test, 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?
Run the tests
Visit the result 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 Enter result button for the test.
Test the new features
Fedora 37 and GNOME 43 include a number of new features that would benefit from testing. 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
Do exploratory testing
Use the latest Fedora 37 Workstation that includes GNOME 43 and see if you can find anything that's crashing or not working correctly. In that case, file a bug!
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.