| Fedora Test Day | |
|---|---|
| |
| Fedora IoT Edition | |
| Date | 2019-03-13 |
| Time | all day |
| Website | QA/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 instalment of Fedora Test Day will focus on Fedora IoT Edition
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - Pwhalen (Pwhalen)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoff Marr (coremodule)
Prerequisites for Test Day
- As of today, the Fedora IoT Edition can be tested by downloading from here [1]
- Enough free space on HDD
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
This is mostly useful for issues with packaging and for issues that need tracking (blocker bugs for F30): Red Hat Bugzilla.
If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.
Test Results
Test results will be transferred once the test day is over