QA:Testcase ABRT sosreport

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
 
|actions=
 
|actions=
 
# Ensure the {{package|sos}} package is installed with the command {{command|su -c 'yum install sos'}}
 
# Ensure the {{package|sos}} package is installed with the command {{command|su -c 'yum install sos'}}
# Edit the config file {{filename|/etc/abrt/abrt_event.conf}}, and comment out lines
+
# {{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
#: #EVENT=post-create
+
#: EVENT=post-create  
#:         nice sosreport --tmp-dir "$DUMP_DIR" --batch \
+
#: nice sosreport --tmp-dir "$DUMP_DIR" --batch \  
#: [...]
+
#: [...]  
 
# Restart the abrtd service: {{command|su -c 'systemctl restart abrtd.service'}}
 
# Restart the abrtd service: {{command|su -c 'systemctl restart abrtd.service'}}
 
# Crash a running application, with the command {{command|pkill -SIGSEGV (appname)}}
 
# Crash a running application, with the command {{command|pkill -SIGSEGV (appname)}}

Revision as of 08:01, 30 March 2011

Description

This test case checks whether sosreport cooperates with ABRT correctly.


How to test

  1. Ensure the Package-x-generic-16.pngsos 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/cache/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