From Fedora Project Wiki

(minor cleanups)
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 'dnf 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>. This is the default, so if you are running a clean live image or have not manually re-configured abrt, it should be there
# Turn on the logger workflow
# If you had to change the file, restart ABRT with the command {{command|su -c 'systemctl restart abrtd.service'}}
<pre>
sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf
</pre>
# 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> or run {{command|will_segfault}}. It must be a process that is part of a signed Fedora package.
# Click on the panel applet to start ''abrt-gui''
# Run '''Problem Reporting''' application.
# Select the entry matching the recently crashed application, then click on '''Open'''
# Select the entry matching the recently crashed application, then click '''Report'''.
# When you reach reporter selector page, select '''Logger'''  
# When you reach reporter selector page, select '''Export the problem data information to a text file'''
# Use "Configure Events" button in the same window to change log file path. The default path, {{filename|/var/log/abrt.log}}, is usually not writable by regular users, so pick somewhere inside your home directory. The file does not have to exist, it will be created
# 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 at the last screen you should see ''"The report was stored 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]]

Latest 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
  1. Confirm that the abrtd and abrt-applet processes are both running
  2. Kill some running process: kill -SIGSEGV (pid) or run will_segfault. It must be a process that is part of a signed Fedora package.
  3. Run Problem Reporting application.
  4. Select the entry matching the recently crashed application, then click Report.
  5. When you reach reporter selector page, select Export the problem data information to a text file
  6. Go through the reporting process until a dialog asking for Log File path appears.
  7. Fill in the path and continue
  8. Click through to the last window of the wizard

Expected Results

  1. After you finish the steps in wizard in the log 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=409561"