|Fedora Test Day|
|Mail • Subscribe • Archives|
What to test?
Today's instalment of Fedora Test Day will focus on GNOME 3.32
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - kalev (kalev)
- Quality Assurance - Adam Williamson (adamw),Sumantro Mukherjee (sumantrom), Kamil Páral (kparal), coremodule (coremodule)
Prerequisites for Test Day
- A fully updated Fedora Image 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!)
- Enough free space on HDD
How to test?
Do exploratory testing
Use the latest Fedora rawhide Workstation that includes GNOME 3.32 and see if you can find anything that's crashing or not working right. In that case, file a bug!
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 three 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 F30): Red Hat Bugzilla.
Second, there's upstream GNOME Bugzilla that's useful for issues that are likely not Fedora-specific. However, GNOME is migrating to gitlab and maybe about 50% of the upstream modules are in a new location.
Third, there's GNOME Gitlab where more and more upstream GNOME modules have migrated.
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.
Test results will be transferred once the test day is over