| Fedora CoreOS Test Day | |
|---|---|
| |
| Fedora CoreOS | |
| Date | TBD |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-coreos (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 Fedora CoreOS
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - Dusty Mabe (dustymabe)
- Quality Assurance - Kamil Paral (kparal), Sumantro Mukherjee (sumantrom), Geoff Marr (coremodule)
For real time help, please join us on the IRC: #fedora-coreos[?] on http://freenode.net
Documentation is also available here. Documentation feedback is welcome through chat, mailing list, github tracker and pagure tracker
Prerequisites for Test Day
- virtual machine (aarch64 or x86_64)
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: CoreOS Bugzilla.
If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-coreos, #fedora-test-day or #fedora-qa and we will help you.
Test Results
The test results will be transferred after the test day is over.