From Fedora Project Wiki
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 56: | Line 56: | ||
=== Run the tests === | === Run the tests === | ||
Open [http://testdays.fedorainfracloud.org/events/140 the test week results page]. Each column title links to a page describing a test to run through. Once you have run through a test, enter your results using the ''Enter result'' button. If you think that you have found an issue, | Open [http://testdays.fedorainfracloud.org/events/140 the test week results page]. Each column title links to a page describing a test to run through. Once you have run through a test, enter your results using the ''Enter result'' button. If you think that you have found an issue, create an issue report, and include the link to the report in the test result. | ||
If possible, try to run through an entire category of tests (a category is an entire row in the table), rather than stopping part of the way through. You can choose to start with whichever category you prefer; try to focus on the categories that have had the least testing. | If possible, try to run through an entire category of tests (a category is an entire row in the table), rather than stopping part of the way through. You can choose to start with whichever category you prefer; try to focus on the categories that have had the least testing. | ||
| Line 83: | Line 83: | ||
== Reporting bugs == | == 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 F37): [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 | 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 == | == Test Results == | ||