| Fedora Test Days | |
|---|---|
| |
| Changes/LUCasPrimaryDownloadable | |
| Date | 2016-04-19 |
| Time | all day |
| Website | QA/Fedora_24_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 testing Fedora Media Writer for different Operating Systems.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Developer1 (irc_nick1), Developer2 (irc_nick2)
- Quality Assurance - Adam Williamson (adamwill) (adamw), Sumantro Mukherjee (sumantro), Tester3 (irc_nick5)
Prerequisite for Test Day
Prerequisite needs for the test event.
- Usb Flash Drive ( Anything above 4 GB )
- Root permission of the system.
- Fedora 22/23/24 Aplha
- An updated Fedora 24 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
How to test?
For Fedora 22/23/24
- Get the package from here
- Install the package
- Download your favorite version of Fedora
- Boot your system with the live USB
- Verify the installation
- Full step by step doc
Update your machine
If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test Cases
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. 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 udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. 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. For each test case, use the result template to enter your result, as shown in the example result line.
| User | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |