From Fedora Project Wiki

Revision as of 04:20, 23 April 2019 by Yisooan (talk | contribs) (Fix result page link)

Upgrade Test Day

Date 2019-04-26
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 instalment of Fedora Test Day will focus on Upgrade Test Day

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to sumantrom.

Prerequisite for Test Day

  • A system (real or virtual) you can install Fedora too, and not mind if it breaks
  • A Fedora 29 image: download Workstation or Server or KDE and other spins
  • For Previous Test Cases: download Fedora 28
  • Make sure to use the latest version of dnf for F28 installed
  • For gnome-software upgrade tests, make sure you have gnome-software-3.28.2-4.fc28 if you are testing F28 to F30 upgrades

How to test?

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

If you have problems with any of the tests, report a bug to Bugzilla usually for the component dnf. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Anaconda will display an error dialog allowing you to report the problem to Bugzilla. This will also automatically attach logs, error message and traceback to the report -- this way of reporting bugs is preferred.

Test Results