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.
Fedora 42 KDE Test Week 2025-03-31
Hey Folks,
As many of you may know, KDE is becoming a blocking deliverable in this release we are hosting The KDE test week[0]. You can still submit the results here[1]. KDE is very important for our community members and testing this way ahead of time helps us find bugs and eliminate them!!
Thanks for testing!
[0] http://fedoraproject.org/wiki/Test_Day:2025-03-31_F42_KDE_Test_Week
[1] https://testdays.fedoraproject.org/events/213
What to test?
This Test Day will focus on KDE
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - Alessandro Astone (aleasto), Marc Deop (marcdeop), Neal Gompa (ngompa)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Kamil Paral (kparal), Adam Williamson (adamw)
- Upstream - Nate Graham (ngraham), Joshua Goins (redstrate)
You can chat with us on Matrix. See the infobox on top of the page to learn where to join.
Prerequisite for Test Day
- A virtual machine or a bare metal machine
- An installation of Fedora 42 KDE ISO. Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.
How to test?
Visit the results 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Reporting bugs
Perhaps you've found an already-reported bug. Please look at:
When filing the bug, it's very helpful to include:
- exact steps you've performed (and whether you can reproduce it again)
- screenshots or videos, if applicable
- system journal (log), which you can retrieve by
journalctl -b > journal.txt- all output in a terminal, if started from a terminal
- your system description
If you are unsure about exactly how to file the report or what other information to include, just ask us.
Please make sure to link to the bug when submitting your test result, thanks!
Test Results
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.
