From Fedora Project Wiki

(convert to new category system)
(abrt 2 changes)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin.
+
|description=This test case tests the functionality of the ABRT feature using the ''Logger'' reporting plugin.
 
|actions=
 
|actions=
 
# Ensure you have the plugin installed with the command {{command|su -c 'yum install abrt-plugin-logger'}}
 
# Ensure you have the plugin installed with the command {{command|su -c 'yum install abrt-plugin-logger'}}
# Edit {{filename|/etc/abrt/abrt.conf}} and be sure the ''Logger'' plugin is enabled in the ''CCpp'' and ''Python'' sections. For example:
+
# Edit {{filename|/etc/abrt/abrt_event.conf}} and be sure you have there e.g. <tt>EVENT=report_Logger                        abrt-action-print -o "${Log_File:-/var/log/abrt.log}"</tt>
#:<pre>
+
# If changed the file, restart ABRT with the command {{command|su -c 'service abrtd restart'}}
#:...
 
#:CCpp = Bugzilla, Logger
 
#:Python = Bugzilla, Logger
 
#:...
 
#:</pre>
 
# Restart ABRT with the command {{command|su -c 'service abrtd restart'}}
 
 
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
 
# Kill a running process with the command {{command|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''
 
# Click on the panel applet to start ''abrt-gui''
# Select the entry matching the recently crashed application, then click on '''Report''', select Logger plugin.
+
# Select the entry matching the recently crashed application, then click on '''Open''', select '''Logger''' plugin.
# At the report window, click '''Send'''
+
# Finish the wizard and save the report to predefined log file (usually {{filename|/var/log/abrt.log}}).
 
|results=
 
|results=
# After you click '''Send''', a notification window should report: "Logger: Report was stored into: /var/log/abrt-logger"
+
# After you finish the steps in wizard at the last screen you should see ''"The report was stored to /var/log/abrt.log"''
# The crash information should in fact be added to that file
+
# Open the log file and see if your crash is in it.
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 12:27, 15 March 2011

Description

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


How to test

  1. Ensure you have the plugin installed with the command su -c 'yum install abrt-plugin-logger'
  2. Edit /etc/abrt/abrt_event.conf and be sure you have there e.g. EVENT=report_Logger abrt-action-print -o "${Log_File:-/var/log/abrt.log}"
  3. If changed the file, restart ABRT with the command su -c 'service abrtd restart'
  4. Confirm that the abrtd and abrt-applet processes are both running
  5. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  6. Click on the panel applet to start abrt-gui
  7. Select the entry matching the recently crashed application, then click on Open, select Logger plugin.
  8. Finish the wizard and save the report to predefined log file (usually /var/log/abrt.log).

Expected Results

  1. After you finish the steps in wizard at the last screen you should see "The report was stored to /var/log/abrt.log"
  2. Open the log file and see if your crash is in it.