(fixed error 404 on Fedora 31 download link) |
(Fix link to latest iso, remove references to gnome bugzilla (everything is in gitlab now), reword and clarify some stuff) |
||
| Line 24: | Line 24: | ||
== Prerequisites for Test Day == | == Prerequisites for Test Day == | ||
* A | * A [https://dl.fedoraproject.org/pub/fedora/linux/development/31/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-31-20190917.n.2.iso Fedora 31 Workstation nightly 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!). It's also fine to use a fully updated Fedora 31 Workstation Beta installation; no need to reinstall your system just for this test day. However, if you are doing a clean install, please use the updated iso here and not the official Beta iso that does not have final GNOME 3.34.0, and instead has older GNOME 3.33.92. | ||
* Enough free space on HDD | * Enough free space on HDD | ||
| Line 30: | Line 31: | ||
=== Do exploratory testing === | === Do exploratory testing === | ||
Use the latest Fedora | Use the latest Fedora 31 Workstation that includes GNOME 3.34 and see if you can find anything that's crashing or not working right. In that case, file a bug! | ||
=== Run the tests === | === Run the tests === | ||
| Line 38: | Line 39: | ||
== Reporting bugs == | == Reporting bugs == | ||
We have | 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 F31): [https://bugzilla.redhat.com Red Hat Bugzilla]. | ||
Second, there's upstream [https://gitlab.gnome.org/ 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. | 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. | ||
Revision as of 06:58, 18 September 2019
| Fedora Test Day | |
|---|---|
| |
| GNOME 3.34 | |
| Date | 2019-09-18 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (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 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 instalment of Fedora Test Day will focus on GNOME 3.34
Who's available?
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 Fedora 31 Workstation nightly 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!). It's also fine to use a fully updated Fedora 31 Workstation Beta installation; no need to reinstall your system just for this test day. However, if you are doing a clean install, please use the updated iso here and not the official Beta iso that does not have final GNOME 3.34.0, and instead has older GNOME 3.33.92.
- Enough free space on HDD
How to test?
Do exploratory testing
Use the latest Fedora 31 Workstation that includes GNOME 3.34 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.
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 F31): 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.