Implement an automated test case in openQA to verify that no automatic error-catching systems report errors in a typical system boot, aligning with the Fedora 42 Final Release Criterion related to SELinux crash notifications.
Test Case Reference: Fedora_42_Final_Release_Criteria#selinux-crash-notifications
Metadata Update from @lruzicka: - Custom field story_points adjusted to 4
we already effectively cover this as best we can. the desktop_notifications tests expect there to be no notifications when running live, and only an update notification after install - if an SELinux or crash notification is present, the test will fail. e.g. https://openqa.fedoraproject.org/tests/3170124#step/desktop_notifications/19 failed because there was a crash notification.
Ok, I wanted to make this to follow the above mentioned test case that is currently not being provided results from openQA, although if, as you are saying, we do the testing.
The link you posted - https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria#SELinux_and_crash_notifications - is a criterion, not a test case. If you open its "References", it says "Test case: QA:Testcase_desktop_error_checks", which is reported based on the results of the desktop_notifications_live and desktop_notifications_postinstall tests - see around https://pagure.io/fedora-qa/fedora_openqa/blob/main/f/src/fedora_openqa/conf_test_suites.py#_1254 .
Metadata Update from @lruzicka: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.