From Fedora Project Wiki

(abrt 2 changes)
No edit summary
(7 intermediate revisions by 5 users not shown)
Line 2: Line 2:
|description=This test case tests the functionality of the ABRT feature using the ''Logger'' reporting 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 libreport-plugin-logger'}}
# 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>
# If changed the file, 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 some 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 ''abrt-gui''
# The ''abrt-applet'' system tray icon should emerge with notification stating "Crash in package foo-1.2.3 has been detected"
# Select the entry matching the recently crashed application, then click on '''Open''', select '''Logger''' plugin.
# Run gnome-abrt in expert mode ''gnome-abrt -x''
# Finish the wizard and save the report to predefined log file (usually {{filename|/var/log/abrt.log}}).
# Select the entry matching the recently crashed application, then click '''Analyze'''.
# When you reach reporter selector page, select '''Logger'''
# Use "Preferences" button in the same window and go to "Events" tab to change log file path. The file does not have to exist, it will be created
# Click through to the last window of the wizard
|results=
|results=
# After you finish the steps in wizard at the last screen you should see ''"The report was stored to /var/log/abrt.log"''
# After you finish the steps in wizard at the last screen you should see ''"The report was stored/appended to <FILENAME>"''
# Open the log file and see if your crash is in it.
# Open the log file and see if crash information is in it and is well-formatted
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 15:15, 2 May 2013

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 libreport-plugin-logger'
  2. Confirm that the abrtd and abrt-applet processes are both running
  3. Kill some running process: kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package.
  4. The abrt-applet system tray icon should emerge with notification stating "Crash in package foo-1.2.3 has been detected"
  5. Run gnome-abrt in expert mode gnome-abrt -x
  6. Select the entry matching the recently crashed application, then click Analyze.
  7. When you reach reporter selector page, select Logger
  8. Use "Preferences" button in the same window and go to "Events" tab to change log file path. The file does not have to exist, it will be created
  9. Click through to the last window of the wizard

Expected Results

  1. After you finish the steps in wizard at the last screen you should see "The report was stored/appended to <FILENAME>"
  2. Open the log file and see if crash information is in it and is well-formatted
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_Logger_plugin&oldid=335013"