From Fedora Project Wiki

(convert to new category system)
(abrt 2 changes)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests that activation of [[Features/ABRT|ABRT]] plugins works correctly.
+
|description=This test case tests that deactivation of ABRT plugins works correctly.
 
|actions=
 
|actions=
# Edit the config files {{filename|/etc/abrt/plugins/*.conf}} and look for lines such as:
+
# Edit the config files {{filename|/etc/abrt/plugins/$plugin.conf}} and look for ''Enabled'' directive and change it:
#:<pre>
+
#:Enabled = no
#:Enabled = yes
+
# Restart abrtd service.
#:</pre>
+
# Crash relevant application; ELF binary in case of CCpp plugin and .py one in case of Python, respectively.
# Try changing some disabled plugins to enabled, and some enabled to disabled
 
# Stop ABRT with the command {{command|su -c 'service abrtd stop'}}
 
# Restart ABRT at a console with the command {{command|su -c 'abrtd -d'}}
 
# Examine the output and note which plugins are ''Registered''
 
 
|results=
 
|results=
# The plugins set as ''Enabled'' should be shown as ''Registered'' when ABRT starts up, and plugins set as ''Disabled'' should not
+
# User is not notified about the crash.
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Revision as of 12:04, 15 March 2011

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.