From Fedora Project Wiki

(abrt plugins test)
 
No edit summary
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{admon/warning|This test is outdated|It was used a time ago and is now obsolete.}}
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] plugins.
|description=This test case tests that deactivation of ABRT plugins works correctly.
|actions=
|actions=
# Edit the config files {{filename|/etc/abrt/plugins/$plugin.conf}} and look for ''Enabled'' directive and change it:
#:Enabled = no
# Restart abrtd service.
# Crash relevant application; ELF binary in case of CCpp plugin and .py one in case of Python, respectively.
|results=
# User is not notified about the crash.


Edit config file  /etc/abrt/abrt.conf, where you should find lines:
Don't forget to revert the change(s).
<pre>
ABRT Plugins:
# enabled plugins
EnabledPlugins = SQLite3, CCpp, Logger
</pre>
 
How to test this: only plugins in EnabledPlugins are loaded, so try to run
<pre># abrt -d </pre>
and you should see what is being loaded and try to fidle with enabled plugins -- if you remove SQLite3 plugin it should complain that it needs some DB plugin.
 
Database Plugin:
<pre>
# selected DB plugin
Database = SQLite3
 
# this option is to ensure, that crashdumps won't take the whole HDD space
MaxCrashReportsSize = 1000;
</pre>
 
How to test this: set this to some lower value and try to generate some crashdumps with abrt and
exceed this limit - the last dump shouldn't be saved
note - the last saved dump can exceed this value, but the next one won't
be saved
 
|results=
ABRT should behave according to the configuration options
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 15:46, 22 September 2011

Warning.png
This test is outdated
It was used a time ago and is now obsolete.


Description

This test case tests that deactivation of ABRT plugins works correctly.


How to test

  1. Edit the config files /etc/abrt/plugins/$plugin.conf and look for Enabled directive and change it:
    Enabled = no
  2. Restart abrtd service.
  3. Crash relevant application; ELF binary in case of CCpp plugin and .py one in case of Python, respectively.

Expected Results

  1. User is not notified about the crash.

Don't forget to revert the change(s).

Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_Plugins&oldid=254228"