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 ' | + | # 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. |
− | # | + | # Run '''Problem Reporting''' application. |
− | + | # Select the entry matching the recently crashed application, then click '''Report'''. | |
− | # Select the entry matching the recently crashed application, then click ''' | + | # When you reach reporter selector page, select '''Export the problem data information to a text file''' |
− | # When you reach reporter selector page, select ''' | + | # 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 | # Click through to the last window of the wizard | ||
|results= | |results= | ||
− | # After you finish the steps in wizard | + | # 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
- Ensure you have the plugin installed with the command
su -c 'dnf install libreport-plugin-logger'
- 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 runwill_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 wizardExpected 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