From Fedora Project Wiki

(Created page with '{{QA/Test_Case |description= This test case checks whether ABRT's SOSreport plugin works correctly. |actions= # Ensure the appropriate packages are installed wi...')
 
No edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=
|description=
This test case checks whether [[Features/ABRT|ABRT's]] SOSreport plugin works correctly.
This test case checks whether sosreport cooperates with ABRT correctly.
|actions=
|actions=
# Ensure the appropriate packages are installed with the command {{command|su -c 'yum install abrt-plugin-sosreport'}}
# Ensure the {{package|sos}} package is installed with the command {{command|su -c 'yum install sos'}}
# Edit the config file {{filename|/etc/abrt/abrt.conf}}, and change the ''ActionsAndReporters'' line to read:
# {{command|sosreport}} is disabled by default, enable it by editing the config file {{filename|/etc/abrt/abrt_event.conf}}, and commenting out line `EVENT=` relevant to {{command|sosreport}}, so you have
#:<pre>
#: EVENT=post-create
#:ActionsAndReporters = SOSreport
#: nice sosreport --tmp-dir "$DUMP_DIR" --batch \
#:</pre>
#: [...]
# restart abrtd {{command|su -c 'service abrtd restart'}}
# Restart the abrtd service: {{command|su -c 'systemctl restart abrtd.service'}}
# kill some app (this time it might take some time (~5s) before the icon appears, as it waits for sosreport to finish)
# Crash a running application, with the command {{command|pkill -SIGSEGV (appname)}}
# Wait for a crash notification to appear: it might take some time (~20 s) before the icon appears, as it waits for sosreport to finish
|results=
|results=
# Verify that the file sosreport.tar.bz2 exists in directory /var/cache/abrt/<the_crash_directory> and has some reasonable content  
# Verify that the file {{filename|sosreport.tar.xz}} exists in directory {{filename|/var/spool/abrt/<the_crash_directory>}} and has some reasonable content  
#* the file should contain config files from /etc/, grub.conf, some info from proc, loaded modules and much more...
# The tarball should contain config files from /etc, grub.conf, some info from /proc, loaded modules, and much more
#* the_crash_directory will be something like ccpp-1270110556-2295 (the format is: <analyzer>-<time>-<pid>)
 
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 12:23, 1 April 2011

Description

This test case checks whether sosreport cooperates with ABRT correctly.


How to test

  1. Ensure the sos package is installed with the command su -c 'yum install sos'
  2. sosreport is disabled by default, enable it by editing the config file /etc/abrt/abrt_event.conf, and commenting out line EVENT= relevant to sosreport, so you have
    EVENT=post-create
    nice sosreport --tmp-dir "$DUMP_DIR" --batch \
    [...]
  3. Restart the abrtd service: su -c 'systemctl restart abrtd.service'
  4. Crash a running application, with the command pkill -SIGSEGV (appname)
  5. Wait for a crash notification to appear: it might take some time (~20 s) before the icon appears, as it waits for sosreport to finish

Expected Results

  1. Verify that the file sosreport.tar.xz exists in directory /var/spool/abrt/<the_crash_directory> and has some reasonable content
  2. The tarball should contain config files from /etc, grub.conf, some info from /proc, loaded modules, and much more
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_sosreport&oldid=230185"