Test Day:2010-04-01 ABRT: Difference between revisions

Revision as of 10:43, 31 March 2010

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 (IRC: jmoskovc)
Quality Assurance - Kparal (IRC: kparal), Michal Nowak (IRC: mnowak)

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 tables below:

QA:Testcase_ABRT - default crash report
QA:Testcase_ABRT_Logger - Logger plugin
QA:Testcase_ABRT_Bugzilla - Bugzilla plugin
QA:Testcase_ABRT_Mailx - Mailx plugin
QA:TestCase ABRT BlackList - package blacklist
QA:Testcase ABRT GPG check - reporting crashes of signed packages only
QA:TestCase ABRT GPG Keys - additional keys for signing packages
QA:Testcase ABRT Actions and Reporters - testing of action/reporting plugins
QA:Testcase ABRT Cron - periodical plugins using Cron
QA:Testcase ABRT Plugins - configuring plugins
QA:Testcase ABRT CLI - CLI interface
QA:Testcase ABRT kernel - kernel oops
QA:Testcase ABRT python - python tracebacks
QA:Testcase ABRT CCPP addon - C/C++ tracebacks

FIXME - update test cases above!

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

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 ^[1]	fail ^[2]	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345

[1] Test pass, but also encountered RHBZ #54321

[2] RHBZ #12345

[1]

[2]

@@ Line 49: / Line 49: @@
 === How to test? ===
+Please follow each of following [[:Category:ABRT_Test_Cases|ABRT Test Cases]] and sum up the results in the tables below:
-High level details on how a contributor can get involved.  This can include (but not limited to):
+# [[QA:Testcase_ABRT]] - default crash report
+# [[QA:Testcase_ABRT_Logger]] - Logger plugin
+# [[QA:Testcase_ABRT_Bugzilla]] - Bugzilla plugin
+# [[QA:Testcase_ABRT_Mailx]] - Mailx plugin
+# [[QA:TestCase ABRT BlackList]] - package blacklist
+# [[QA:Testcase ABRT GPG check]] - reporting crashes of signed packages only
+# [[QA:TestCase ABRT GPG Keys]] - additional keys for signing packages
+# [[QA:Testcase ABRT Actions and Reporters]] - testing of action/reporting plugins
+# [[QA:Testcase ABRT Cron]] - periodical plugins using Cron
+# [[QA:Testcase ABRT Plugins]] - configuring plugins
+# [[QA:Testcase ABRT CLI]] - CLI interface
+# [[QA:Testcase ABRT kernel]] - kernel oops
+# [[QA:Testcase ABRT python]] - python tracebacks
+# [[QA:Testcase ABRT CCPP addon]] - C/C++ tracebacks
-* Areas to target with exploratory testing
+'''FIXME - update test cases above!'''
-* A list of pre-defined test cases to execute
-* How to report back results
-=== Test Cases ===
+'''FIXME - add Improved Python Debugging test case according to [https://fedorahosted.org/fedora-qa/ticket/55#comment:3 jmoskovc's comment].'''
-Provide a list of test areas or test cases that you'd like contributors to execute.  See [[:Category:ABRT Test Cases]].
 === Test Results ===
+Please report all bugs into [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=abrt Bugzilla] against the '''abrt''' component.
-Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include a link where to report bugs. For example:
+''' FIXME - update column count and their headers according to final test case list.'''
-Please report all bugs into [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Bugzilla] against the '''abrt''' component.
 {|
 ! User
-! Smolt Profile
 ! [[QA:Testcase_sample_1|Sample test 1]]
 ! [[QA:Testcase_sample_2|Sample test 2]]
@@ Line 74: / Line 83: @@
 ! References
 |-
-| [[User:FasUser]]
+| [[User:Sample User|Sample User]]
-| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
+| {{result|none}}
-| PASS
+| {{result|pass}}
-| PASS
+| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
-| FAIL <ref>See {{bz|12345}}</ref>
+| {{result|fail}} <ref>{{bz|12345}}</ref>
-| PASS
 | <references/>
 |-

Search