Test Day:2010-04-01 ABRT

DATE	TIME	WHERE
2010-04-01	From 12:00 to 21:00 UTC (8am -> 5pm EDT)	#fedora-test-day (webirc)

DELETE-ME: Last test day page for inspiration.

What to test?

Today's installment of Fedora Test Day will focus on Automated Bug Reporting Tool (ABRT). This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. ABRT is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file.

Bottom line: do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and kill them easily at close range.

ABRT should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

• Development - Jiří Moskovčák (jmoskovc), Nikola Pajkovsky (npajkovs), Denys Vlasenko (dvlasenk), Karel Klíč (kklic)
• Quality Assurance - Kamil Páral (kparal), Michal Nowak (mnowak), Adam Williamson (adamw)

Prerequisite for Test Day

You will need either fully updated Fedora 13 system or a custom live image for ABRT.

Fedora 13 installation

1. If you don't already have existing Fedora 13 installation, you may install from Fedora 13 Beta RC2.

2. Then add ABRT development repository:

wget 'fixme' -O /etc/yum.repos.d/abrt.repo
wget 'fixme' -O /etc/pki/rpm-gpg/RPM-GPG-KEY-abrt

3. Fully upgrade:

yum upgrade

ABRT live image

This is a non-destructive live image that you just download, burn to CD/DVD and boot from it. You can also make a bootable USB stick from it by using liveusb-creator.

Architecture	SHA256
i686	fixme
x86_64	fixme

How to test?

Please follow each of following ABRT Test Cases and sum up the results in the table below:

1. QA:Testcase_ABRT - default crash report
2. QA:Testcase_ABRT_Logger - Logger plugin
3. QA:Testcase_ABRT_Bugzilla - Bugzilla plugin
4. QA:Testcase_ABRT_Mailx - Mailx plugin
5. QA:TestCase ABRT BlackList - package blacklist
6. QA:Testcase ABRT GPG check - reporting crashes of signed packages only
7. QA:TestCase ABRT GPG Keys - additional keys for signing packages
8. QA:Testcase ABRT Actions and Reporters - testing of action/reporting plugins
9. QA:Testcase ABRT Cron - periodical plugins using Cron
10. QA:Testcase ABRT Plugins - configuring plugins
11. QA:Testcase ABRT CLI - CLI interface
12. QA:Testcase ABRT kernel - kernel oops
13. QA:Testcase ABRT python - python tracebacks
14. QA:Testcase ABRT CCPP addon - C/C++ tracebacks

FIXME - update test cases above! sort them in some meaningful order!

FIXME - add Improved Python Debugging test case according to jmoskovc's comment.

Close all fake bugs you create!
During certain test cases you will be required to simulate application crashes and report these crashes into Bugzilla. It is very important that after every such fake report you open the link provided by ABRT and close that bug as NOTABUG with comment like "ABRT testing bug". Otherwise you would overload package developers with fake bug reports. Thank you.

Test Results

Please report all bugs into Bugzilla against the abrt component.

FIXME - update column count and their headers according to final test case list.

User	Sample test 1	Sample test 2	Sample test 3	Sample test 4	References
Sample User	none	pass	warn	fail