From Fedora Project Wiki

Line 2: Line 2:
 
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature.
 
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature.
 
|actions=
 
|actions=
# We will check that the ''KerneloopsScanner'', works and provides correct amount of crashes detected.
+
# We will check that the ''dumpoops works and provides correct amount of crashes detected.
 
# Download files:
 
# Download files:
 
#* [http://git.fedorahosted.org/git/abrt.git?p=abrt.git;a=blob_plain;f=examples/oops1.test;hb=HEAD oops1.test]
 
#* [http://git.fedorahosted.org/git/abrt.git?p=abrt.git;a=blob_plain;f=examples/oops1.test;hb=HEAD oops1.test]
Line 9: Line 9:
 
#* [http://git.fedorahosted.org/git/abrt.git?p=abrt.git;a=blob_plain;f=examples/not_oops2.test;hb=HEAD not_oops2.test]
 
#* [http://git.fedorahosted.org/git/abrt.git?p=abrt.git;a=blob_plain;f=examples/not_oops2.test;hb=HEAD not_oops2.test]
 
#* [http://git.fedorahosted.org/git/abrt.git?p=abrt.git;a=blob_plain;f=examples/not_oops3.test;hb=HEAD not_oops3.test]
 
#* [http://git.fedorahosted.org/git/abrt.git?p=abrt.git;a=blob_plain;f=examples/not_oops3.test;hb=HEAD not_oops3.test]
# Test that stand-alone detector tool is working properly:
+
# Test that stand-alone detector tool is working properly:  
<pre>
+
<pre>
$ dumpoops -s oops1.test
+
$ dumpoops -s oops1.test
dumpoops: found oopses: 1
+
dumpoops: found oopses: 1
Version: 2.6.27.9-159.fc10.i686 #1
+
Version: 2.6.27.9-159.fc10.i686 #1
BUG: unable to handle kernel NULL pointer dereference at 00000000
+
BUG: unable to handle kernel NULL pointer dereference at 00000000
...
+
...</pre>
</pre>
+
 
oops1.test and oops3.test should contain one and three oopses respectively. not_oopsN.test should not be detected as containing oops.
+
 
# Optional. 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>
+
 
 +
# And now test if ABRT's ''KernelOopsScanner'' is working
 +
# 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 oops1.test >> /var/log/messages</pre>
 
# cat the downloaded file to /var/log/messages e.g.:<pre>cat oops1.test >> /var/log/messages</pre>
 
#* you'll need root privs for this
 
#* you'll need root privs for this
Line 25: Line 27:
  
 
|results=
 
|results=
# Oopses detected and visible in abrt-gui
+
# 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.
 +
# After finishing the second part: oopses detected and visible in abrt-gui
 
}}
 
}}
 
[[Category:ABRT_Test_Cases]]
 
[[Category:ABRT_Test_Cases]]

Revision as of 14:14, 1 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 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
  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 oops1.test >> /var/log/messages
    • you'll need root privs for this
  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