Test Day:2017-04-06 AnacondaBlivetGUI

AnacondaBlivetGUI
Date	2017-03-30
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 installment of Fedora Test Day will focus on Blivet-GUI in Anaconda

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.

• Development - Vojtěch Trefný
• Quality Assurance - Adam Williamson (adamw), Mike Ruckman (roshi), gmarr (coremodule), Sumantro Mukherjee (sumantrom)

Prerequisite for Test Day

• An updated Fedora 26 Alpha 1.7 workstation

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

Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component blivet-gui. 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

Please enter your results on the result page. The results will be transferred here after the Test Day is finished.