From Fedora Project Wiki

 
(21 intermediate revisions by 9 users not shown)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature using the ''Logger'' plugin.
+
|description=This test case tests the functionality of the ABRT feature using the ''Logger'' reporting plugin.
 
|actions=
 
|actions=
Edit <code>/etc/abrt/abrt.conf</code> and list the ''Logger'' plugin in ''EnabledPlugins'', ''CCpp'' and ''Python'' lines (which will enable and activate it). For example:
+
# Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-logger'}}
 +
# Turn on the logger workflow
 
<pre>
 
<pre>
...
+
sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf
EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
 
...
 
CCpp = Bugzilla, Logger
 
Python = Bugzilla, Logger
 
...
 
 
</pre>
 
</pre>
Make sure you have abrt-plugin-logger installed. Install this plugin if it's missing.
+
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
Restart ABRT: <pre># service abrt restart</pre>
+
# 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.
And final steps are:
+
# Select the entry matching the recently crashed application, then click '''Report'''.
# Ensure that the ''abrt'' and ''abrt-applet'' processes are both running
+
# When you reach reporter selector page, select '''Export the problem data information to a text file'''
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
+
# Go through the reporting process until a dialog asking for Log File path appears.
# Click on the panel applet to start ''abrt-gui''
+
# Fill in the path and continue
# Select the entry matching the recently crashed application, then click on '''Report'''
+
# Click through to the last window of the wizard
# At the report window, click '''Send'''
 
 
|results=
 
|results=
# After you click '''Send''', a notification window should report, among other things: "Logger: Report was stored into: /var/log/abrt-logger"
+
# 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
 
}}
 
}}
[[Category: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