From Fedora Project Wiki
mNo edit summary |
(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/ | |description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin. | ||
|actions= | |actions= | ||
Edit ''/etc/ | 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 = | BlackList = | ||
# enabled plugins | # enabled plugins | ||
EnabledPlugins = SQLite3, CCpp, Mailx | # there has to be exactly one database plugin | ||
# | EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx | ||
# Database | |||
Database = SQLite3 | Database = SQLite3 | ||
</pre> | </pre> | ||
Restart ABRT: <pre># service restart | Restart ABRT: <pre># service abrt restart</pre> | ||
And final steps are: | And final steps are: | ||
# Ensure that the '' | # 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 '' | # Click on the panel applet to start ''abrt-gui'' | ||
# Select the entry matching the recently crashed application, select ''' | # 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/ | # 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:
- Ensure that the abrt and abrt-applet processes are both running
- Kill a running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
- Click on the panel applet to start abrt-gui
- Select the entry matching the recently crashed application, select Generate
- At the report window, click Apply
Expected Results
- A crash log should be reported by the Logger plugin into /var/log/abrt-logger