(Download links were set opposite. aarch64 download link was set on text of x86_64 and vice-versa.) |
|||
(One intermediate revision by one other user not shown) | |||
Line 27: | Line 27: | ||
== Prerequisites for Test Day == | == Prerequisites for Test Day == | ||
* for | * for AArch64 download the [https://dl.fedoraproject.org/pub/alt/iot/test/33/IoT/aarch64/images/Fedora-IoT-33-20200925.0.aarch64.raw.xz disk image] or [https://dl.fedoraproject.org/pub/alt/iot/test/33/IoT/aarch64/iso/Fedora-IoT-IoT-ostree-aarch64-33-20200925.0.iso iso] | ||
* for | * for x86_64 download [https://dl.fedoraproject.org/pub/alt/iot/test/33/IoT/x86_64/images/Fedora-IoT-33-20200925.0.x86_64.raw.xz disk image] or [https://dl.fedoraproject.org/pub/alt/iot/test/33/IoT/x86_64/iso/Fedora-IoT-IoT-ostree-x86_64-33-20200925.0.iso iso] | ||
* Enough free space on HDD | * Enough free space on HDD | ||
Line 46: | Line 46: | ||
[[Category:Fedora 33 Test Days]] | [[Category: Fedora 33 Test Days]] |
Latest revision as of 20:00, 29 September 2020
Fedora Test Day | |
---|---|
Fedora 33 IoT Edition | |
Date | 2020-09-30 |
Time | all day |
Website | QA/Test Days |
IRC | #fedora-iot (webirc) |
Mailing list | test |
What to test?[edit]
Today's installment of Fedora Test Day will focus on Fedora 33 IoT Edition
Who's available?[edit]
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)
For real time help, please join us on the IRC: #fedora-iot[?] on http://freenode.net
Documentation is also available here. Documentation feedback is welcome through chat, mailing list, or as an issue.
Prerequisites for Test Day[edit]
- for AArch64 download the disk image or iso
- for x86_64 download disk image or iso
- Enough free space on HDD
How to test?[edit]
Run the tests[edit]
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[edit]
This is mostly useful for issues with packaging and for issues that need tracking (blocker bugs for F33): Red Hat Bugzilla under "IoT".
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.