QA:Testcase ABRT Mailx plugin

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(ABRT 2 updates)
 
(12 intermediate revisions by 8 users not shown)
Line 2: Line 2:
 
|description=This test case tests the functionality of the ABRT feature using the ''Mailx'' plugin.
 
|description=This test case tests the functionality of the ABRT feature using the ''Mailx'' plugin.
 
|actions=
 
|actions=
# Ensure you have the plugin installed with the command {{command|su -c 'yum install abrt-plugin-mailx'}} as well as {{package|mailx}} package.
+
# Ensure you have the plugin installed with the command {{command|su -c 'yum install libreport-plugin-mailx'}}
# '''FIXME!!!''' Open {{filename|/etc/abrt/abrt_event.conf}} to see if there's similar line: <tt>'''!!!'''</tt>
+
# Ensure you have sendmail installed with the command {{command|su -c 'yum install sendmail'}}
# Open {{filename|/etc/abrt/plugins/Mailx.conf}} and make sure the configuration is valid:
+
#: Enabled = yes
+
#: EmailFrom = user@localhost
+
#: EmailTo = root@localhost
+
#: SendBinaryData = no
+
# Restart ABRT with the command{{command|su -c 'service abrtd restart'}}
+
# Make sure the sendmail service is running with the command {{command|su -c 'service sendmail start'}} (or, if you use a different MTA, ensure it is running)
+
 
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
 
# Ensure 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. Or use older crash you may have from previous testing.
+
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package
# Click on the panel applet to start ''abrt-gui''
+
# Start gnome-abrt (either from cmdline or from application menu).
# Select the entry matching the recently crashed application, click '''Open''', choose '''Mailx''' reporter
+
# Select the entry matching the recently crashed application, then choose '''Analyze'''.
# Finish the reporting
+
# At reporting step, choose '''Mailx''' as a reporting event
 +
# Use '''Preferences''' button in the same window to configure the plugin, set your email as the recipient.
 +
# Proceed to reporting using "Forward"/"Apply" buttons.
 +
# 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}}).
 
|results=
 
|results=
# An email reporting the crash should be sent to the email address specified in {{filename|/etc/abrt/plugins/Mailx.conf}}. If you left this set to ''root@localhost'', you should be able to see the mail in the file {{filename|/var/spool/mail/root}} in a default Fedora setup or via command ''mail'' as a root.
+
# Check the the email if the message from ABRT has arrived (might take a few minutes).
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Latest 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).