From Fedora Project Wiki

 
(26 intermediate revisions by 10 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 ''/etc/abrt/abrt.conf'' to '''enable''' (i.e. list in EnabledPlugins) and '''activate''' (i.e. list in CCpp line of AnalyzerActionsAndReporters) the ''Logger'' plugin in ''Common'' section.  A sample config is noted below
+
# Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-logger'}}
 +
# Turn on the logger workflow
 
<pre>
 
<pre>
[ Common ]
+
sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf
# Enable GPG check
 
EnableOpenGPG = no
 
# GPG keys
 
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
 
# blacklisted packages
 
BlackList =
 
# enabled plugins
 
# there has to be exactly one database plugin
 
EnabledPlugins = Logger, SQLite3, CCpp, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python #, Mailx
 
# Database
 
Database = SQLite3
 
 
 
[ AnalyzerActionsAndReporters ]
 
CCpp = Bugzilla, Logger
 
 
</pre>
 
</pre>
Restart ABRT: <pre># service abrt restart</pre>
+
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
 
+
# 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.
And final steps are:
+
# Run '''Problem Reporting''' application.
# Ensure that the ''abrt'' and ''abrt-applet'' processes are both running
+
# Select the entry matching the recently crashed application, then click '''Report'''.
# Kill a running process: <tt>kill -SIGSEGV (pid)</tt>. It must be a process that is part of a signed Fedora package
+
# When you reach reporter selector page, select '''Export the problem data information to a text file'''
# Click on the panel applet to start ''abrt-gui''
+
# Go through the reporting process until a dialog asking for Log File path appears.
# Select the entry matching the recently crashed application, select '''Generate'''
+
# Fill in the path and continue
# At the report window, click ''Apply''
+
# Click through to the last window of the wizard
 
|results=
 
|results=
# A crash log should be reported by the ''Logger'' plugin 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