From Fedora Project Wiki

(fix up the final step of the process, remove unnecessary stuff from results)
 
(34 intermediate revisions by 12 users not shown)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/CrashCatcher|Crash Catcher]] 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/crash-catcher/crash-catcher.conf'' to '''enable''' and '''activate''' the ''Logger'' plugin.  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>
# Enable GPG check
+
sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_logger.conf
EnableOpenGPG = no
 
# GPG keys
 
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
 
# blacklisted packages
 
BlackList = bash, bind, apache2
 
# enabled plugins
 
EnabledPlugins = SQLite3, CCpp, Mailx, Logger
 
# selected DB plugin
 
Database = SQLite3
 
# reporters association
 
CCpp = Logger, Mailx
 
 
</pre>
 
</pre>
# Ensure that the ''crash-catcher'' and ''cc-applet'' processes are both running
+
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running
# Kill a 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.
# Click on the panel applet to start ''cc-gui''
+
# Run '''Problem Reporting''' application.
# Select the entry matching the recently crashed application, select '''Forward'''
+
# Select the entry matching the recently crashed application, then click '''Report'''.
# At the report window, click ''Apply''
+
# 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
 
|results=
 
|results=
# A crash log should be reported by the ''Logger'' plugin into ''/var/log/crash-catcher-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:Crash_Catcher_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