From Fedora Project Wiki

(convert to new category system)
(doh)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] quota option.
|description=This test case tests the functionality of the ABRT "quota" option.
|actions=
|actions=


# Edit /etc/abrt/abrt.conf and find this line:
# Edit {{filename|/etc/abrt/abrt.conf}} and find this line: <tt>MaxCrashReportsSize = 1000</tt>, this means that the quota is set to 1000 MB.
<pre>
# Set quota to a lower value (e.g. 1 MB: change the line to read <tt>MaxCrashReportsSize = 1</tt>)
MaxCrashReportsSize = 1000
# Restart the abrtd service with the command {{command|su -c 'systemctl restart abrtd.service'}}
</pre>
# Run a complex GUI application such as Evolution
* this means that the quota is set to 1000MB
# Crash the application: for Evolution, run {{command|pkill -SIGSEGV evolution}}
 
# Try this two or three times
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=
|results=
# ABRT should not save the new crash
# ABRT may save the '''first''' crash exceeding quota but with every other crash the older one should be gone and replaced by the new one
# If abrt-applet is running then it should notify user about exceeded quota
# If abrt-applet is running then it should notify user about both the crash and the exceeded quota
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 17:12, 29 March 2011

Description

This test case tests the functionality of the ABRT "quota" option.


How to test

  1. Edit /etc/abrt/abrt.conf and find this line: MaxCrashReportsSize = 1000, this means that the quota is set to 1000 MB.
  2. Set quota to a lower value (e.g. 1 MB: change the line to read MaxCrashReportsSize = 1)
  3. Restart the abrtd service with the command su -c 'systemctl restart abrtd.service'
  4. Run a complex GUI application such as Evolution
  5. Crash the application: for Evolution, run pkill -SIGSEGV evolution
  6. Try this two or three times

Expected Results

  1. ABRT may save the first crash exceeding quota but with every other crash the older one should be gone and replaced by the new one
  2. If abrt-applet is running then it should notify user about both the crash and the exceeded quota
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_quota&oldid=229627"