QA:Testcase ABRT kernel addon

Description

This test case tests the functionality of the ABRT kerneloops feature.

How to test

1. We will check that the abrt-dump-oops works and provides correct amount of crashes detected.
2. Download files:
   • cut_here.test
   • not_oops3.test
3. Test that stand-alone detector tool works properly; Do as a root for both files:

   $ abrt-dump-oops -d -o cut_here.test

   Version: 2.6.32-19.el6.x86_64

   WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467

   generic_get_mtrr+0x11e/0x140() (Not tainted)

   ...

   [<ffffffff810abcff>] sys_init_module+0xdf/0x250

   [<ffffffff81013172>] system_call_fastpath+0x16/0x1b

   abrt-dump-oops: Creating dump directories

4. Open abrt-gui and look for the crash.
5. And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
6. Make sure /etc/abrt/abrt_event.conf contains EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops and EVENT=report analyzer=Kerneloops abrt-action-kerneloops. If changed anything, restart abrtd: service abrtd restart.
7. cat the downloaded file to /var/log/messages e.g.:

   cat cut_here.test >> /var/log/messages

8. If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.

Expected Results

1. After running abrt-dump-oops on cut_here.test crash should be craeted nad visible via abrt-gui and in the terminal. Running the same command on not_oops3.test should not create crash case.
2. After finishing the second part: oops was detected and is visible in abrt-gui.