From Fedora Project Wiki

(create mailx plugin test case)
 
No edit summary
(34 intermediate revisions by 11 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 ''Mailx'' plugin.
|description=This test case tests the functionality of the ABRT feature using the ''Mailx'' plugin.
|actions=
|actions=
# Edit ''/etc/crash-catcher/crash-catcher.conf'' to '''enable''' and '''activate''' the ''Mailx'' plugin. This is in fact the default, but check in case. A sample config is noted below
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-mailx'}}
<pre>
# Ensure you have sendmail installed with the command {{command|su -c 'yum install sendmail'}}
# Enable GPG check
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
EnableOpenGPG = no
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
# GPG keys
# Start gnome-abrt (either from cmdline or from application menu).
OpenGPGPublicKeys = /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
# Select the entry matching the recently crashed application, then choose '''Analyze'''.
# blacklisted packages
# At reporting step, choose '''Mailx''' as a reporting event
BlackList = bash, bind, apache2
# Use '''Preferences''' button in the same window to configure the plugin, set your email as the recipient.
# enabled plugins
# Proceed to reporting using "Forward"/"Apply" buttons.
EnabledPlugins = SQLite3, CCpp, Mailx
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}}).
# selected DB plugin
Database = SQLite3
# reporters association
CCpp = Mailx
</pre>
# Edit ''/etc/crash-catcher/plugins/Mailx.conf'' and make sure the configuration is valid. The default configuration:
<pre>
# Configuration to Email reporter plugin
# Parameters
Parameters =
 
# Your Email
EmailFrom = user@localhost
 
# Email To
EmailTo = root@localhost
 
# Warning! enabling this may cause sending a lot of MB via email
SendBinaryData = no
</pre>
should work. Only change the EmailTo address to a public address that would require forwarding through a real SMTP server if you have the 'mailx' configuration set so that such mails are correctly handled.
# Ensure that the ''crash-catcher'' and ''cc-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
# Click on the panel applet to start ''cc-gui''
# Select the entry matching the recently crashed application, select '''Forward'''
# At the report window, click ''Apply''
|results=
|results=
# A mail reporting the crash should be sent to the email address specified in ''/etc/crash-catcher/plugins/Mailx.conf''. If you left this set to ''root@localhost'', you should be able to see the mail in the file ''/var/spool/mail/root'' in a default Fedora setup.
# Check the the email if the message from ABRT has arrived (might take a few minutes).
}}
}}
[[Category:Crash_Catcher_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 12:39, 7 May 2013

Description

This test case tests the functionality of the ABRT feature using the Mailx plugin.


How to test

  1. Ensure you have the plugin installed with the command su -c 'yum install libreport-plugin-mailx'
  2. Ensure you have sendmail installed with the command su -c 'yum install sendmail'
  3. Ensure that the abrtd and abrt-applet processes are both running
  4. Kill a running process with the command kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package
  5. Start gnome-abrt (either from cmdline or from application menu).
  6. Select the entry matching the recently crashed application, then choose Analyze.
  7. At reporting step, choose Mailx as a reporting event
  8. Use Preferences button in the same window to configure the plugin, set your email as the recipient.
  9. Proceed to reporting using "Forward"/"Apply" buttons.
  10. If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from the GUI report window, or retrieved from event_log file in problem data directory (e.g. /var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log).

Expected Results

  1. Check the the email if the message from ABRT has arrived (might take a few minutes).
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_Mailx_plugin&oldid=335842"