Test Day:2021-03-17 Fedora 34 GNOME 40

Fedora Test Day
GNOME 40
Date	2021-03-17 to 2021-03-19
Time	all day
Website	QA/Test Days
IRC	#fedora-test-day (webirc)
Mailing list	test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on GNOME 40

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), coremodule (coremodule)

Prerequisites for Test Day

• Fedora 34 Workstation test day iso image with GNOME 40.rc 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 40.rc, which is newer than what's on regular nightly iso images.

• If you already have Fedora 34 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 GNOME 40.rc mega-update.

• Enough free space on HDD

How to test?

Do exploratory testing

Use the latest Fedora 34 Workstation that includes GNOME 40.rc. and see if you can find anything that's crashing or not working correctly. In that case, file a bug!

Test cases

Run through the gnome-shell test cases. Warning, test cases are outdated. Try the best with testing.

What to focus on?

The updated activities overview. Try recreating a typical desktop session and setup the desktop how you'd like it, then run through some typical window and workspace operations. This can include:

• Adding favourites to the dash
• Reorganising the app grid
• Launching apps through search, the dash, the app grid
• Moving windows between workspaces
• Switching workspaces
• Organising and closing workspaces
• Navigating the system using different input devices and methods: super key, shortcuts, touchpad gestures, pointer
  • Entering and exiting the overview
  • Entering and exiting the app grid
  • Moving between workspaces

If testing on bare metal, multi-monitor testing is also encouraged.

Shortcuts and gestures

Shortcuts that are expected to work in the updated overview design:

• Open the overview: Super, Super+↑
• Open the app grid: Super+↑ (from the overview)
• Close the app grid or overview: Super+↓
• Switch workspace:
  • Super+Alt+←/→, Super+PgUp/PgDown, Ctrl+Alt+←/→
  • In the overview: scroll wheel
  • Out of the overview: Super+scroll wheel

Touchpad gestures that are expected to work (depending on your setup, gestures might not work in a VM):

• Open the overview: 3 finger swipe up
• Open the app grid: 3 finger swipe up from overview
• Close the app grid or overview: 3 finger swipe down
• Switch workspace: 3 finger swipe left/right

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.

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 F34): 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.