From Fedora Project Wiki

(adjust associated_release_criterion template invocation)
(we should probably switch this test to journalctl now.)
Line 12: Line 12:
# If you are using a graphical environment, open a terminal window.
# If you are using a graphical environment, open a terminal window.
# Check if system logging facility is working ({{command|tail}} can be replaced with {{command|less}} in the following):  
# Check if system logging facility is working ({{command|tail}} can be replaced with {{command|less}} in the following):  
## {{command| su -c 'tail /var/log/messages'}}  
## {{command| su -c 'journalctl -a'}}  
## {{command| su -c 'tail /var/log/secure'}}  
## {{command| su -c 'tail /var/log/secure'}}  


Revision as of 05:35, 12 December 2013

Associated release criterion
This test case is associated with the Basic_Release_Criteria#system-logging release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case tests if system logging infrastructure is available and working as expected.

Setup

  1. Install Fedora using one of the following methods:
    1. Boot ISO: QA/TestCases/InstallSourceBootIso
    2. DVD: QA/TestCases/InstallSourceDvd
    3. Live Image: QA:TestCases/Install_Source_Live_Image
  2. If necessary, reboot your system after the installation.

How to test

  1. If you are using a graphical environment, open a terminal window.
  2. Check if system logging facility is working (tail can be replaced with less in the following):
    1. su -c 'journalctl -a'
    2. su -c 'tail /var/log/secure'

Expected Results

  1. Log files should not be empty.
  2. The last entries in logs should correspond to the current date and time.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_base_system_logging&oldid=364185"