From Fedora Project Wiki

Line 6: Line 6:
 
# Kill some running process: <tt>kill -SIGSEGV (pid)</tt>. 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.
 
# The ''abrt-applet'' system tray icon should emerge with notification stating "Crash in package foo-1.2.3 has been detected"
 
# The ''abrt-applet'' system tray icon should emerge with notification stating "Crash in package foo-1.2.3 has been detected"
# Click on the notification should to open ''abrt-gui''
+
# Run gnome-abrt in expert mode ''gnome-abrt -x''
# Select the entry matching the recently crashed application, then choose '''Problem > Open problem data''' in main menu.
+
# Select the entry matching the recently crashed application, then click '''Analyze'''.
 
# When you reach reporter selector page, select '''Logger'''
 
# When you reach reporter selector page, select '''Logger'''
# Use "Preferences" button in the same window to change log file path. The file does not have to exist, it will be created
+
# 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
 
# Click through to the last window of the wizard
 
|results=
 
|results=

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