From Fedora Project Wiki

(don't reference obsolete test cases)
Line 4: Line 4:
 
|description=This test case tests if system logging infrastructure is available and working as expected.
 
|description=This test case tests if system logging infrastructure is available and working as expected.
 
|setup=
 
|setup=
# Install Fedora using one of the following methods:
+
# Install Fedora according to [[QA:Testcase_Boot_default_install]], using one of the release-blocking media (e.g. Workstation live image or Server DVD).
## Boot ISO: [[QA/TestCases/InstallSourceBootIso]]
 
## DVD: [[QA/TestCases/InstallSourceDvd]]
 
## Live Image: [[QA:TestCases/Install_Source_Live_Image]]
 
 
# If necessary, reboot your system after the installation.  
 
# If necessary, reboot your system after the installation.  
 
|actions=  
 
|actions=  
Line 13: Line 10:
 
# 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 'journalctl -a'}}  
 
## {{command| su -c 'journalctl -a'}}  
# If rsyslog is installed (for example, on the Server Product), check:
+
# If rsyslog is installed (for example, on the Server Flavor), check:
 
## {{command| su -c 'tail /var/log/secure'}}  
 
## {{command| su -c 'tail /var/log/secure'}}  
  

Revision as of 21:15, 7 February 2015

Note.png
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 according to QA:Testcase_Boot_default_install, using one of the release-blocking media (e.g. Workstation live image or Server DVD).
  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'
  3. If rsyslog is installed (for example, on the Server Flavor), check:
    1. 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.