|Fedora Test Day|
|Date||2022-02-28 to 2022-03-07|
What to test?
Today's installment of Fedora Test Day will focus on GNOME 42
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), coremodule (coremodule)
Prerequisites for Test Day
- Fedora 36 Workstation test day iso image with GNOME 42.beta either on bare metal or in VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!). Note that the test day image provided here includes GNOME 42.beta, which is newer than what's on regular nightly iso images.
- If you already have Fedora 36 Workstation installed, there's no need to reinstall, but just make sure to update to latest updates-testing, in particular make sure you have the update for GNOME 42.beta
- Enough free space on HDD
How to test?
Do exploratory testing
Use the latest Fedora 36 Workstation that includes GNOME 42.beta and see if you can find anything that's crashing or not working correctly. In that case, file a bug!
Run through the gnome-shell test cases. Warning, test cases are outdated. Try the best with testing.
What to focus on?
- System-wide Dark Style Preference
- Updated Folder Icon Theme
- GNOME Text Editor (Replaces gedit)
- Improvements to the Screenshot UI and Native Screen Recording
- Wallpapers for Dark/Light Theme
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.
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 F36): 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.