From Fedora Project Wiki

m
(match > abrt-0.0.4)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/CrashCatcher|Crash Catcher]] feature using the ''Logger'' plugin.
+
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin.
 
|actions=
 
|actions=
Edit ''/etc/crash-catcher/crash-catcher.conf'' to '''enable''' and '''activate''' the ''Logger'' plugin.  A sample config is noted below
+
Edit ''/etc/abrt/abrt.conf'' to '''enable''' and '''activate''' the ''Logger'' plugin in ''Common'' section.  A sample config is noted below
 
<pre>
 
<pre>
 +
[ Common ]
 
# Enable GPG check
 
# Enable GPG check
 
EnableOpenGPG = no
 
EnableOpenGPG = no
Line 9: Line 10:
 
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
 
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
 
# blacklisted packages
 
# blacklisted packages
BlackList = bash, bind, apache2
+
BlackList =
 
# enabled plugins
 
# enabled plugins
EnabledPlugins = SQLite3, CCpp, Mailx, Logger
+
# there has to be exactly one database plugin
# selected DB plugin
+
EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
 +
# Database
 
Database = SQLite3
 
Database = SQLite3
# reporters association
 
CCpp = Logger, Mailx
 
 
</pre>
 
</pre>
Restart ABRT: <pre># service restart abrt </pre>
+
Restart ABRT: <pre># service abrt restart</pre>
  
 
And final steps are:
 
And final steps are:
# Ensure that the ''crash-catcher'' and ''cc-applet'' processes are both running
+
# Ensure that the ''abrt'' and ''abrt-applet'' processes are both running
 
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
 
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
# Click on the panel applet to start ''cc-gui''
+
# Click on the panel applet to start ''abrt-gui''
# Select the entry matching the recently crashed application, select '''Forward'''
+
# Select the entry matching the recently crashed application, select '''Generate'''
 
# At the report window, click ''Apply''
 
# At the report window, click ''Apply''
 
|results=
 
|results=
# A crash log should be reported by the ''Logger'' plugin into ''/var/log/crash-catcher-logger''
+
# A crash log should be reported by the ''Logger'' plugin into ''/var/log/abrt-logger''
 
}}
 
}}
 
[[Category:ABRT_Test_Cases]]
 
[[Category:ABRT_Test_Cases]]

Revision as of 08:53, 18 August 2009

Description

This test case tests the functionality of the ABRT feature using the Logger plugin.


How to test

Edit /etc/abrt/abrt.conf to enable and activate the Logger plugin in Common section. A sample config is noted below

[ Common ]
# Enable GPG check
EnableOpenGPG = no
# GPG keys
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
# blacklisted packages
BlackList =
# enabled plugins
# there has to be exactly one database plugin
EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
# Database
Database = SQLite3

Restart ABRT:

# service abrt restart

And final steps are:

  1. Ensure that the abrt and abrt-applet processes are both running
  2. Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  3. Click on the panel applet to start abrt-gui
  4. Select the entry matching the recently crashed application, select Generate
  5. At the report window, click Apply

Expected Results

  1. A crash log should be reported by the Logger plugin into /var/log/abrt-logger