From Fedora Project Wiki

No edit summary
(proof)
Line 1: Line 1:
{{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 activation of [[Features/ABRT|ABRT]] plugins works correctly.
|actions=
|actions=
 
# Edit the config files {{filename|/etc/abrt/plugins/*.conf}} and look for lines such as:
Go thru the config files /etc/abrt/plugins/*.conf and look for line:
#:<pre>
<pre>
#:Enabled = yes
Enabled = yes
#:</pre>
</pre>
# Try changing some disabled plugins to enabled, and some enabled to disabled
 
# Stop ABRT with the command {{command|su -c 'service abrtd stop'}}
How to test this: only plugins with this line in their config file should be loaded by abrt daemon at startup
# Restart ABRT at a console with the command {{command|su -c 'abrtd -d'}}
<pre>
# Examine the output and note which plugins are ''Registered''
# service abrtd stop
# abrtd -d
</pre>
and you should see what is being '''Registered''' and then try to fiddle with enabled plugins
 
|results=
|results=
ABRT should behave according to the configuration options.
# The plugins set as ''Enabled'' should be shown as ''Registered'' when ABRT starts up, and plugins set as ''Disabled'' should not
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:ABRT_Test_Cases]]

Revision as of 05:25, 1 April 2010

Description

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


How to test

  1. Edit the config files /etc/abrt/plugins/*.conf and look for lines such as:
    Enabled = yes
  2. Try changing some disabled plugins to enabled, and some enabled to disabled
  3. Stop ABRT with the command su -c 'service abrtd stop'
  4. Restart ABRT at a console with the command su -c 'abrtd -d'
  5. Examine the output and note which plugins are Registered

Expected Results

  1. The plugins set as Enabled should be shown as Registered when ABRT starts up, and plugins set as Disabled should not