Per #151, we are missing a test case for the Alpha release criterion "A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project". We should create a test case to validate this criterion, and add it to the matrices.
I've just created a test-case for rsyslog the default fedora logging daemon.
https://fedoraproject.org/wiki/QA:Testcase_rsyslog
That's a good rsyslog-specific test case, but we may want to have a more generic one which will still apply even if we change the default system logger, for use in the release validation matrix.
Replying to [comment:2 adamwill]:
Without the name of logging daemon you can't check if it's running and enabled by default, but we can check if system logging facility is working by looking into /var/log/{secure,messages}
If you've an idea how generic should be the test-case, please develop the idea so I can write more generic test-case.
"but we can check if system logging facility is working by looking into /var/log/{secure,messages}"
that's the thing: this is what the criterion actually requires. in theory system logging could be implemented by some mechanism other than a daemon (though I can't think what, off the top of my head), and the criterion still satisfied. the key point is that the system logs should exist and be populated with the appropriate messages, so that's what the release criteria validation test case should check. Really, I think just a test case that says 'do an install, boot the installed system, check that /var/log/messages exists' (roughly, you can fill in the details :>) would be enough. I don't think it's necessary to look for some specific process to be running.
Please check if the following test-case is OK:
https://fedoraproject.org/wiki/QA:Testcase_system_logging
looks pretty good to me, nice work! might want to call it QA:Testcase_base_system_logging just to match up with the other 'base' tests, but that's not super important. Might want to add an explicit 'open a terminal' step too, just for maximum hand-holding value =). I tend to like suggesting the command:
su -c 'tail /var/log/messages'
instead of the two-step process, just because it's easier to write and less prone to misunderstanding.
Edited and moved to:
https://fedoraproject.org/wiki/QA:Testcase_base_system_logging
Note that 'open a terminal' is for users using DE/WM, but the test can be done from text-only installation (headless server, etc...)
This test case is in production in the Base matrix, closing.
Login to comment on this ticket.