From Fedora Project Wiki

Revision as of 18:30, 20 April 2017 by Chrismurphy (talk | contribs) (Intel results (x86_64 / i686))

Fedora Media Writer

Date 2017-04-20
Time all day

Website QA/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 installment of Fedora Test Day will focus on Fedora Media Writer. Fedora Media Writer, is used for creating bootable flash drives on different operating systems and architectures. The tool is the primary download option for Fedora Workstation since Fedora 25. Since the Fedora 25 cycle, support for writing ARM images has been added to Media Writer. In this test day, we aim to test creation of Fedora 25 and Fedora 26 pre-release boot media on Windows, macOS, and various Fedora releases, with a focus on creation of ARM-bootable media.

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

Data loss
Any data on the USB stick or memory card used for this test is likely to be destroyed. Please do not use a stick whose contents you need to keep.
  • USB flash drive or (micro)SD card for ARM testing (min. 4GiB)
  • Root access on the system used to write the drive (or admin access in Windows)
  • The latest version of the tool for one of the test platforms (see next section)
  • A system to test booting on (for testing ARM images, you will need a supported ARM system)

Getting the latest version

The minimum required Fedora Media Writer version for testing during the test day is 4.0.95.

You can verify which version you have either by checking your packaging system or by unrolling the title screen and scrolling to the bottom.

How to update?

There are three ways to get the latest version in Fedora:

In Windows and macOS, use the following link: . There you can download the latest package for your system.

There are also experimental .deb packages for Ubuntu and Debian.

How to test?

Run the tests

Visit the QA Test case page and follow the instructions there to install the tool, write an image, and test that it boots. Ideally, try writing several different images, and running the tool on different platforms (Windows, macOS, and Fedora).

Once you have completed your tests, add your results to the Results tables below, following the example results from the first line as a template. There are two tables, one for results from writing ISO images for Intel platforms (x86_64 / i686), the other for writing disk images for ARM systems. The first column should be your name with a link to your User page in the Wiki if you have one. For each platform you tested writing an image from, use the result template to enter your result, as shown in the example result line.

To be clear, if you write an image for booting on an Intel system and test boot it on an Intel system, enter your result in the first table ("Intel results"), in the column matching the platform you wrote the image from. If you write an image for booting on an ARM system and test boot it on an ARM system, enter your result in the second table ("ARM results"), in the column matching the platform you wrote the image from. You don't have to enter a result in every column - just test as many platforms as you can, and leave the columns for platforms you can't test blank.

Exploratory testing

If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.

Reporting bugs

If you have problems with any of the tests, report a bug to Bugzilla usually for the component mediawriter. Please also make the bug 'block' the tracker bug for issues with the tool, by putting '1310542' in the Blocks: field. 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.

Test Results

Intel results (x86_64 / i686)

User Profile Fedora Windows macOS References
Sample User Description of test system(s)
Pass pass
Warning warn
Fail fail
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
siddharthvipul1 Fedora 26 alpha 1.7
Pass pass
prakashmishra1598 Fedora 26 alpha 1.7
Pass pass
lbrabec Fedora 26
Pass pass
pschindl Fedora 26
Pass pass
cmurf macOS 10.12.3
Warning warn
Cite error: Closing </ref> missing for <ref> tag
Fail fail
  1. RHBZ #12345
siddharthvipul1 Fedora 26 alpha 1.7
Pass pass
lbrabec Fedora 26
Fail fail
  1. RHBZ #1443981