From Fedora Project Wiki

Revision as of 04:44, 21 April 2015 by Adamwill (talk | contribs) (throw together some kind of viable format really quickly)

Fedora Test Days

Date 2015-04-21
Time all day

Website QA/Fedora_22_test_days
IRC #fedora-test-day (webirc)

Mailing list

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 FedUp

Who's available

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

Prerequisite for Test Day

A system with Fedora 20 or 21 you can use for test purposes (i.e. you don't mind if it all goes wrong and you lose the system)! Testing with a virtual machine will be useful for many cases, and will let you run multiple tests easily.

How to test?

The test procedure is simply to take a Fedora 20 or Fedora 21 installation and upgrade it to Fedora 22. To ensure you get the latest fedup for testing, run yum --enablerepo=updates-testing install fedup or yum --enablerepo=updates-testing update fedup first. To upgrade, run fedup --network 22 --instrepo, where (arch) is the appropriate architecture (armhfp, x86_64, or i386).

The idea is to test upgrades from as many different starting situations as possible - particularly with different package sets, languages, keyboard layouts, and storage configurations.

If the upgrade completes successfully, test the upgraded system to ensure it works correctly.

Test Results

If any of your upgrades fails (or leads to a broken system), report a bug to Bugzilla. The correct component will depend on the exact nature of the bug - ask in IRC if you're unsure. If you can't find out what component to file against, file the bug against usually for the component fedup. Include any useful details about the system's configuration, and note that your result is part of this Test Day and mention that you followed the instructions on this page.

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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. In the 'Results' column, you can link to bug reports of any failed tests, and very briefly summarize your results. Please don't post long comments here, it will make the table hard to read: anything longer than a few words is likely fodder for a bug report, or mailing list post, or you can use <ref>comment</ref> to make the comment appear as a footnote below the table.

User Results
Sample User 2 pass 2 fail, RHBZ #12345 RHBZ #54321