| GNOME 44 Apps | |
|---|---|
| |
| Date | 2023-03-09 to 2023-03-10 |
| Time | all day |
| Website | QA/Test Days |
| Matrix | #workstation:fedoraproject.org |
| IRC | #fedora-workstation (webirc) |
| Mailing list | test |
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, 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?
This Test Day will focus on GNOME 44 Apps.
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) FIXME
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on Matrix or IRC. See the infobox on top of the page to learn where to join.
Prerequisites for Test Day
- Fedora 38 Workstation nightly ISO image installed on either bare metal or in a virtual machine. (Make sure you have no important data on that system. Things might go wrong -- don't do this on your production machine!)
- If you already have Fedora 38 Workstation installed, there's no need to reinstall, but just make sure you have the latest updates installed.
How to test?
Visit the results 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Fedora 38 and GNOME 44 include a number of new features that would benefit from additional testing. These include: FIXME
Reporting bugs
All bugs should be reported into the GNOME bug tracker. A less-preferred alternative is to file them into Red Hat Bugzilla. Each application has its own separate project, just search for it.
When filing the bug, it's very helpful to include:
- exact steps you've performed (and whether you can reproduce it again)
- screenshots or videos, if applicable
- system journal (log), which you can retrieve by
journalctl -b > journal.txt - all output in a terminal, if started from a terminal
- your system description
If you are unsure about exactly how to file the report or what other information to include, just ask us.
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!
Test Results
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.