From Fedora Project Wiki

No edit summary
No edit summary
 
(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.
<ol>
# '''!!!FIXME!!!''' Open {{filename|/etc/abrt/abrt_event.conf}} to see if there's similar line: <tt>'''!!!'''</tt>
  <li>Ensure you have the plugin installed with the command {{command|su -c 'dnf install libreport-plugin-mailx'}}</li>
# Open {{filename|/etc/abrt/plugins/Mailx.conf}} and make sure the configuration is valid:
  <li>Ensure you have sendmail installed with the command {{command|su -c 'dnf install sendmail'}}</li>
#: Enabled = yes
  <li>Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running</li>
#: EmailFrom = user@localhost
  <li>Turn on the mailx workflow <pre>sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_mailx.conf</pre></li>
#: EmailTo = root@localhost
  <li>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</li>
#: SendBinaryData = no
  <li>Start gnome-abrt (either from cmdline or from application menu)</li>
# Restart ABRT with the command{{command|su -c 'service abrtd restart'}}
  <li>Select the entry matching the recently crashed application, then choose '''Report'''</li>
# 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)
  <li>At reporting step, choose '''Send the problem data via email''' as a reporting event</li>
# Ensure that the ''abrtd'' and ''abrt-applet'' processes are both running
  <li>Update Subject, Sender and Recepient</li>
# 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.
  <li>Proceed to reporting using "Forward"/"Apply" buttons</li>
# Click on the panel applet to start ''abrt-gui''
  <li>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}})</li>
# Select the entry matching the recently crashed application, click '''Open''', choose '''Mailx''' reporter
</ol>
# Finish the reporting
|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 11:42, 10 April 2015

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 'dnf install libreport-plugin-mailx'
  2. Ensure you have sendmail installed with the command su -c 'dnf install sendmail'
  3. Ensure that the abrtd and abrt-applet processes are both running
  4. Turn on the mailx workflow
    sudo sed -i 's/# EVENT/EVENT/' /etc/libreport/workflows.d/report_mailx.conf
  5. Kill some running process: kill -SIGSEGV (pid) or run will_segfault. It must be a process that is part of a signed Fedora package
  6. Start gnome-abrt (either from cmdline or from application menu)
  7. Select the entry matching the recently crashed application, then choose Report
  8. At reporting step, choose Send the problem data via email as a reporting event
  9. Update Subject, Sender and Recepient
  10. Proceed to reporting using "Forward"/"Apply" buttons
  11. 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).