To participate in the Test Day, individuals must have access to either a virtual machine or a bare metal machine with the Fedora 42 KDE ISO installed. Participants are encouraged to follow the test case instructions provided on the results page, and any bugs encountered should be reported through the Fedora 42 Final blocker bugs, including detailed information such as reproduction steps, screenshots, system logs, and system descriptions. The results from the testing will be compiled and shared after the event concludes.
Key figures in the community will be available for support, including developers Alessandro Astone, Marc Deop, and Neal Gompa, as well as quality assurance members Sumantro Mukherjee, Kamil Paral, and Adam Williamson, along with upstream contributors Nate Graham and Joshua Goins. Participants can join discussions via Matrix.
To prepare for the Test Day, participants should ensure that their systems are fully updated, and if they are performing a fresh install, they should use the latest nightly image. The testing process involves running specific test cases from the results page and documenting any outcomes. Participants are also encouraged to explore beyond predefined test cases.
For bug reporting, it is essential to check for existing reports before submitting a new one. When submitting a bug report, detailed steps and relevant materials should be included to facilitate troubleshooting. Test results will be exported for review after the event.
In summary, the Fedora 42 KDE Test Week presents an excellent opportunity for community engagement and improvement of the KDE experience. Participants are encouraged to actively contribute to the testing process and collaborate with team members to enhance the overall quality of the Fedora release
Fedora 42 KDE Test Week 2025-03-31
The Fedora Quality Engineering team is organizing a Fedora 42 KDE Test Week on March 31, 2025. This event is significant for community members, as KDE is evolving into a critical deliverable. The test day will concentrate on KDE and will include participants from development, quality assurance, upstream, and development teams. The requirements for the test day consist of either a virtual machine or a bare metal machine, along with the installation of the Fedora 42 KDE ISO. Please proceed to the results page and adhere to the instructions provided for each test case to conduct the test. Should you encounter a bug, please report it through the Fedora 42 Final blocker bugs. Ensure to include pertinent details such as steps to reproduce, screenshots, system journal, output, and a description of your system. The test results will be exported following the conclusion of the test day.