From Fedora Project Wiki

(rewrite (hope this is right, the original is shortened and unclear))
(don't show up in Category:Package_abrt_test_cases)
 
(4 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
|description=
 
|description=
 
This test case checks whether [[Features/ABRT|ABRT's]] actions and reporters function works correctly.
 
This test case checks whether [[Features/ABRT|ABRT's]] actions and reporters function works correctly.
 +
{{admon/warning|Please disregard this test case.|This test case was written for ABRT 1 which has already been replaced by ABRT 2.}}
 
|actions=
 
|actions=
 
# Ensure the appropriate packages are installed with the command {{command|su -c 'yum install abrt-plugin-runapp abrt-plugin-mailx'}}
 
# Ensure the appropriate packages are installed with the command {{command|su -c 'yum install abrt-plugin-runapp abrt-plugin-mailx'}}
Line 8: Line 9:
 
#:ActionsAndReporters = RunApp("ls", "ls-output")
 
#:ActionsAndReporters = RunApp("ls", "ls-output")
 
#:</pre>
 
#:</pre>
 +
{{admon/warning|The following test doesn't work|There is a regression in abrt that prevents this option to work.}}
 
# Set up an executable-specific report action in the ''AnalyzerActionsAndReporters'' section, such as:
 
# Set up an executable-specific report action in the ''AnalyzerActionsAndReporters'' section, such as:
 
#:<pre>
 
#:<pre>
Line 19: Line 21:
 
# Run the specified command (gedit in our example) and then kill it with the command {{command|kill -SIGSEGV (pid)}}
 
# Run the specified command (gedit in our example) and then kill it with the command {{command|kill -SIGSEGV (pid)}}
 
|results=
 
|results=
# Verify that a directory listing appears in the file {{filename|ls-output}} '''FIXME: Where should this file be?'''
+
# Verify that a directory listing appears in the file {{filename|ls-output}} located at /var/cache/abrt/<the_crash_directory>
# Verify that the Mailx plugin was used to send a mail about the crash
+
#* the_crash_directory will be something like ccpp-1270110556-2295 (the format is: <analyzer>-<time>-<pid>)
 +
# -- DOESN'T WORK --Verify that the Mailx plugin was used to send a mail about the crash
 
}}
 
}}
[[Category:ABRT_Test_Cases]]
 

Latest revision as of 06:37, 19 September 2018

Description

This test case checks whether ABRT's actions and reporters function works correctly.

Warning.png
Please disregard this test case.
This test case was written for ABRT 1 which has already been replaced by ABRT 2.


How to test

  1. Ensure the appropriate packages are installed with the command su -c 'yum install abrt-plugin-runapp abrt-plugin-mailx'
  2. Edit the config file /etc/abrt/abrt.conf, and change the ActionsAndReporters line to read:
    ActionsAndReporters = RunApp("ls", "ls-output")
Warning.png
The following test doesn't work
There is a regression in abrt that prevents this option to work.
  1. Set up an executable-specific report action in the AnalyzerActionsAndReporters section, such as:
    [ AnalyzerActionsAndReporters ]
    # all C/C++ crashes will be reported via Logger plugin
    CCpp = Logger
    # if gedit crashes, then an email will be send and Logger (from ''CCpp'' section) should be silent
    CCpp:gedit = Mailx("[abrt] Gedit crashed")
  2. Restart ABRT with the command su -c 'service abrtd restart'
  3. Run the specified command (gedit in our example) and then kill it with the command kill -SIGSEGV (pid)

Expected Results

  1. Verify that a directory listing appears in the file ls-output located at /var/cache/abrt/<the_crash_directory>
    • the_crash_directory will be something like ccpp-1270110556-2295 (the format is: <analyzer>-
  2. -- DOESN'T WORK --Verify that the Mailx plugin was used to send a mail about the crash