Fwd: F43 Beta RC1 is here, please participate in test coverage

[Kamil Paral]

Hello IoT team,
I sent out the forwarded email (see below) as a request to all relevant
Fedora teams. In the IoT case, things are a little different:

* The regular compose doesn't include IoT, so I guess you'll test the
latest one, and then perhaps also the one that has all updates currently in
general RC1 but not stable yet.
* The latest wiki matrix that was nominated and created is this one:
https://fedoraproject.org/wiki/Test_Results:Current_IoT_General_Test
* The testcase statistics have a different link for IoT, this one:
https://openqa.fedoraproject.org/testcase_stats/43iot/

Thanks a lot for your testing.
Kamil Paral
Fedora Quality

Please don't forget to read the email below:

---------- Forwarded message ---------
From: Kamil Paral 
Date: Wed, Sep 10, 2025 at 2:13 PM
Subject: F43 Beta RC1 is here, please participate in test coverage
To: test , devel <
[e-mail]>, desktop ,
KDE on Fedora discussion , <
[e-mail]>, , Fedora
List

Hello,
the first F43 Beta RC is here, and we need to make sure it works well. The
Go/NoGo meeting is happening tomorrow [1].

All important information and links are in this announcement:
https://lists.fedoraproject.org/archives/list/[e-mail]...

The test coverage tool is important, it can show what was tested fairly
recently, or not in a long time, so that people can focus their attention
the right way. It has sections related to particular editions (Desktop,
Server, Cloud) and general sections (Installation - which is not just
Anaconda, but also e.g. upgrades; and Base system functionality).

Available automation (coconut, anaconda-bot) tries to populate many fields,
but it doesn't have full coverage. Please focus on empty fields. For Beta,
ideally all Basic and Beta test cases should be marked as passing. Testing
Final test cases is optional at this point, but very appreciated.

The linked BlockerBugs website [2] displays current blockers and freeze
exceptions bugs. Any help debugging, fixing and verifying those is very
welcome. If you've found a new bug, please add it to the wiki matrix (if it
corresponds to one of the test cases), and you can also propose it as a
blocker using the same BlockerBugs tool (if you find it really important,
or you find it violating some of release criteria - the tool will guide
you).

With any questions, please reach out [3].

Thank you!
Kamil Paral
Fedora Quality

[1] https://calendar.fedoraproject.org/Fedora%20release/
[2] https://qa.fedoraproject.org/blockerbugs/
[3] https://fedoraproject.org/wiki/QA#Communicate