From Fedora Project Wiki

(Create F40 IoT test week page)
 
Line 33: Line 33:
=== Run the tests ===
=== Run the tests ===


Visit the [http://testdays.fedorainfracloud.org/events/170 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.
Visit the [https://testdays.fedoraproject.org/events/178 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 ==
== Reporting bugs ==

Revision as of 16:46, 6 March 2024

Fedora 40 IoT Test Week
Echo-testing-48px.png
Fedora 40 IoT Edition

Date 2024-03-18 to 2024-03-22
Time 5 days

Website QA/Fedora_40_test_days
Mailing list test


Note.png
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 Fedora 40 IoT Edition

Who's available?

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Documentation is available here. Documentation feedback is welcome through chat, mailing list, or as an issue.

Prerequisites for Test Day

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 40): Red Hat Bugzilla under "IoT".