Latest revision as of 15:46, 22 September 2011

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.

Edit the config files /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.

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

@@ Line 1: / Line 1: @@
+{{admon/warning|This test is outdated|It was used a time ago and is now obsolete.}}
 {{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=
-# 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=
-# 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.
+Don't forget to revert the change(s).
 }}
-[[Category:ABRT_Test_Cases]]
+[[Category:Package_abrt_test_cases]]