From Fedora Project Wiki
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 libreport-plugin-logger'}}
# Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-logger'}}
# Turn on the logger workflow
<pre>
sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf
</pew>
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
# 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> or run {{command|will_segfault}}. 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"
# Run '''Problem Reporting''' application.
# Run gnome-abrt in expert mode ''gnome-abrt -x''
# Select the entry matching the recently crashed application, then click '''Report'''.
# Select the entry matching the recently crashed application, then click '''Analyze'''.
# When you reach reporter selector page, select '''Export the problem data information to a text file'''
# When you reach reporter selector page, select '''Logger'''
# Go through the reporting process until a dialog asking for Log File path appears.
# 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
# Fill in the path and continue
# Click through to the last window of the wizard
# 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/appended to <FILENAME>"''
# After you finish the steps in wizard in the log you should see ''"The report was stored/appended to <FILENAME>"''
# Open the log file and see if crash information is in it and is well-formatted
# 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 11:34, 10 April 2015

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 'dnf install libreport-plugin-logger'
  2. Turn on the logger workflow
sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf
</pew>
# Confirm that the abrtd and abrt-applet processes are both running
# Kill some running process: kill -SIGSEGV (pid) or run will_segfault. It must be a process that is part of a signed Fedora package.
# Run Problem Reporting application.
# Select the entry matching the recently crashed application, then click Report.
# When you reach reporter selector page, select Export the problem data information to a text file
# Go through the reporting process until a dialog asking for Log File path appears.
# Fill in the path and continue
# Click through to the last window of the wizard


Expected Results

# After you finish the steps in wizard in the log you should see "The report was stored/appended to <FILENAME>"
# 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=409560"