From Fedora Project Wiki

 
(5 intermediate revisions by 3 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.
  
Go thru the config files /etc/abrt/plugins/*.conf and look for line:
+
Don't forget to revert the change(s).
<pre>
 
Enabled = yes
 
</pre>
 
 
 
How to test this: only plugins with this line in their config file should be loaded by abrt daemon
 
<pre>
 
# service abrtd stop
 
# abrtd -d
 
</pre>
 
and you should see what is being '''Registered''' and then try to fiddle with enabled plugins
 
 
 
|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).