From Fedora Project Wiki

(Add links to GNOME bug tracker and mention exploratory testing)
m (Minor fixes)
Line 38: Line 38:
== Reporting bugs ==
== Reporting bugs ==


We have three places to file bugs. First, in downstream in Fedora bug tracker. This is mostly useful for issues with packaging and for issues that need tracking downstream (blocker bugs for F28): [https://bugzilla.redhat.com Red Hat Bugzilla].
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 F28): [https://bugzilla.redhat.com Red Hat Bugzilla].


Second, there's upstream [https://bugzilla.gnome.org.com 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.
Second, there's upstream [https://bugzilla.gnome.org 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 [https://gitlab.gnome.org/ GNOME Gitlab] where more and more upstream GNOME modules have migrated.
Third, there's [https://gitlab.gnome.org/ GNOME Gitlab] where more and more upstream GNOME modules have migrated.

Revision as of 13:31, 25 March 2018

Fedora Test Day
Echo-testing-48px.png
GNOME 3.28

Date 2018-03-26
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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 3.28

Who's available?

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Prerequisites for Test Day

  • A fully updated Fedora 28 Workstation 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 latest Fedora 28 Workstation that includes GNOME 3.28.0 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 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 F28): 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