QA:Testcase ABRT kernel addon

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (filename corrected from the download link)
m (replace $ by # because need to be restarted as root)
Line 19: Line 19:
  
  
# And now test if ABRT's ''KernelOopsScanner'' is working
+
# And now test if ABRT's ''KernelOopsScanner'' is working, you'll need root privs for this
# Edit /etc/abrt/abrt.conf so it says: <pre>10 = KerneloopsScanner</pre> This makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:<pre>$ service abrtd restart</pre>
+
# Edit /etc/abrt/abrt.conf so it says: <pre>10 = KerneloopsScanner</pre> This makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:<pre># service abrtd restart</pre>
 
# cat the downloaded file to /var/log/messages e.g.:<pre>cat examples_oops1.test >> /var/log/messages</pre>
 
# cat the downloaded file to /var/log/messages e.g.:<pre>cat examples_oops1.test >> /var/log/messages</pre>
#* you'll need root privs for this
 
 
# Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops
 
# Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops
 
# Open the abrt-gui and check if you can see the oops
 
# Open the abrt-gui and check if you can see the oops

Revision as of 22:21, 5 April 2010

Description

This test case tests the functionality of the ABRT feature.


How to test

  1. We will check that the dumpoops works and provides correct amount of crashes detected.
  2. Download files:
  3. Test that stand-alone detector tool is working properly:
 $ dumpoops -s examples_oops1.test
 dumpoops: found oopses: 1
 Version: 2.6.27.9-159.fc10.i686 #1
 BUG: unable to handle kernel NULL pointer dereference at 00000000
 ...


  1. And now test if ABRT's KernelOopsScanner is working, you'll need root privs for this
  2. Edit /etc/abrt/abrt.conf so it says:
    10 = KerneloopsScanner
    This makes abrtd scan /var/log/messages more often, every 10 secs. Then restart abrtd:
    # service abrtd restart
  3. cat the downloaded file to /var/log/messages e.g.:
    cat examples_oops1.test >> /var/log/messages
  4. Wait for abrt-applet (make sure it's running) to show the notification about the detected kerneloops
  5. Open the abrt-gui and check if you can see the oops

Expected Results

  1. After running dumpoops: oops1.test and oops3.test should contain one and three oopses respectively. not_oopsN.test should not be detected as containing oops.
  2. After finishing the second part: oopses detected and visible in abrt-gui