From Fedora Project Wiki

Revision as of 02:41, 7 February 2015 by Adamwill (talk | contribs) (initial version of the test day page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Fedora Test Days
Anaconda and Dnf

Date 2015-02-12
Time all day

Website Fedora Calendar
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 DNF use in Anaconda, the Fedora installer. DNF is the package manager intended to replace yum as the default for Fedora soon: part of the goal of this test day is to decide if it is in good enough shape to replace yum for Anaconda for Fedora 22.

Who's available

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

Prerequisite for Test Day

  • Rawhide nightly image(s) (links to come)
  • Test system / drive or virtual machine (for this test day, you need something you can lose all the data from, non-destructive testing is not possible)
  • (Optional) a server for hosting kickstarts

How to test?

Download one of the nightly images to be used for testing, and run through one or more of the test cases listed #Test Results below. You can also do free form testing to exercise the package-related functions of the installer as much as possible: try different things in the INSTALLATION SOURCE and SOFTWARE SELECTION screens, and exercise the kickstart directives relating to repositories and package sets.

Reporting bugs

If you have problems with any of the tests, report a bug to Bugzilla for the appropriate component. Likely choices are:

If you are unsure about which component to report a bug against, 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. For each test case, use the result template to enter your result, as shown in the example result line.

Test Results

User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User
Pass pass
Warning warn
Fail fail
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345