(→Test Results: Fix category setting) |
(→Reporting bugs: Reword to make more clear this is about upstream bug tracker) |
||
Line 49: | Line 49: | ||
* [https://qa.fedoraproject.org/blockerbugs/milestone/40/final/buglist Fedora 40 Final blocker bugs] | * [https://qa.fedoraproject.org/blockerbugs/milestone/40/final/buglist Fedora 40 Final blocker bugs] | ||
All new bugs should be reported into the '''[https://bugs.kde.org KDE bug tracker]'''. A less-preferred alternative is to file them into '''[https://bugzilla.redhat.com Red Hat Bugzilla]'''. General desktop issues are generally reported against <code>plasmashell</code>, but each component has its own "product" | All new bugs should be reported into the '''[https://bugs.kde.org KDE bug tracker]'''. A less-preferred alternative is to file them into '''[https://bugzilla.redhat.com Red Hat Bugzilla]'''. General desktop issues are generally reported against <code>plasmashell</code> in the KDE bug tracker, but each component has its own "product" there. | ||
{{admon/tip | We really need bug reports! | Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!}} | {{admon/tip | We really need bug reports! | Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!}} |
Revision as of 13:45, 20 January 2024
KDE Plasma6 | |
---|---|
![]() | |
Date | 2024-01-29 to 2024-02-05 |
Time | all day |
Website | QA/Test Days |
Matrix | #test-day:fedoraproject.org(other clients|?) |
Mailing list | test |
What to test?
This Test Day will focus on Changes/KDE Plasma 6
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - aleasto (aleasto), marcdeop (marcdeop), ngompa (ngompa)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
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 40 KDE RC1. 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:
All new bugs should be reported into the KDE bug tracker. A less-preferred alternative is to file them into Red Hat Bugzilla. General desktop issues are generally reported against plasmashell
in the KDE bug tracker, but each component has its own "product" there.
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.