From Fedora Project Wiki

m
(Removed draft notices and removed duplicate documentation found in ABRT feature page)
Line 1: Line 1:
{{draft}}
 
 
{{admon/important|If you can somehow improve quality of this document, please join the fight and help}}
 
 
 
 
 
{|border="1"
 
{|border="1"
 
|-style="color: white; background-color: #3074c2; border:1px; font-weight: bold"  
 
|-style="color: white; background-color: #3074c2; border:1px; font-weight: bold"  
Line 13: Line 7:
 
|}
 
|}
  
 
+
== What to test? ==
== Testing ABRT ==
 
  
 
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.
 
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.
Line 20: Line 13:
  
 
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.
 
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.
 
We will test:
 
 
* ABRT GUI;
 
* compiled (C/C++) programs support;
 
* Python programs support;
 
* detection if apps are from supported packages;
 
* using configured plugins:
 
** database plugin;
 
** bugzilla plugin (report crash to bugzilla);
 
** file transfer plugin (transfer crash data via network);
 
** mailx plugin (send mail when crash happens);
 
** kernel oops plugin;
 
** RunApp plugin (run arbitrary application when crash happens).
 
  
 
== Who's available ==
 
== Who's available ==
Line 41: Line 20:
 
* Quality Assurance - [[User:dpravec| David Pravec]], [[User:kparal| Kamil Páral]], [[User:jlaska| James Laska]]
 
* Quality Assurance - [[User:dpravec| David Pravec]], [[User:kparal| Kamil Páral]], [[User:jlaska| James Laska]]
  
== Prerequisite for Test Day ==
+
== What's needed to test ==
  
You will need to get current ABRT (select your method):
+
* A system with some kind of network connection
# install latest ABRT from Rawhide
+
* [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or the live CD available for this test day (again see below).
# install latest ABRT from its development repository on Fedora 11
+
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
'''<<FIXME: for now we have only internal [[RedHat]] IP server, setup public repository!>>'''. For Redhat internal abrt development server create /etc/yum.repos.d/abrt.repo containing:
 
  
<pre>
+
== How to test? ==
[abrt]
 
name=ABRT
 
baseurl=http://10.34.33.153/$releasever/$basearch/
 
gpgcheck=0
 
enabled=1
 
</pre>
 
# download and burn ABRT Testing CD ([http://fedorapeople.org/~dpravec/testdays/2009-08-20_ABRT/ ISO images] will be available at least 24 hours before the test day starts)
 
  
{{admon/important| Note: for reporting to work well, you should have a ''fully-updated system'' (Fedora 11 or Rawhide). Reporting uses <code>-debuginfo</code> packages, which have to match the version of the corresponding crashed program's packages. This also avoids reporting a bug which has already been fixed in a later version of the software. }}
+
=== '''Update your machine''' ===
  
 +
See the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
  
== ABRT Documentation ==
+
=== '''Live Image''' ===
 
* [https://fedoraproject.org/wiki/Features/ABRTF12 ABRT features, overview]
 
* [https://fedorahosted.org/abrt/wiki ABRT Home page] (trac wiki)
 
* [http://fedoraproject.org/w/uploads/a/ab/ABRT.odp ABRT FUDCon Berlin 2009 presentation]
 
* ABRT was in the past called [[Features/CrashCatcher|CrashCatcher]]
 
  
== How to start using ABRT  ==
+
Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
  
Install abrt and plugins:
+
{|
<pre># yum install abrt-desktop</pre>
+
! Architecture !! SHA256
 +
|-
 +
| [FIXME i686] || FIXME
 +
|-
 +
| [FIXME x86-64] || FIXME
 +
|}
  
This is not needed when you will use [http://fedorapeople.org/~dpravec/testdays/2009-08-20_ABRT/ ABRT TestDay Live CD].
+
=== Test Cases ===
{{admon/important| After installation of ABRT you should ''reboot'' your computer to have everything working properly.}}
 
  
<pre>
+
Follow each of following [[:Category:ABRT_Test_Cases]] and report your findings in the tables below.
# chkconfig abrt on
 
# reboot
 
</pre>
 
  
=== Test basic functionality ===
 
 
Now if something crashes, ABRT will handle the crash. If you want to  test this, crash something, for example:
 
<pre>
 
$ xfontsel &
 
$ killall -6 xfontsel
 
</pre>
 
 
An icon will appear in the notification area.
 
You can now run the GUI:
 
<pre>
 
$ abrt-gui &
 
</pre>
 
 
Now select the crash, click "report" to report it, or click "delete" to delete it.
 
 
=== ABRT Test Cases to be tested ===
 
 
<!-- Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
 
-->
 
 
Available tests include:
 
 
* [[QA:Testcase_ABRT]] - default crash report
 
* [[QA:Testcase_ABRT]] - default crash report
 
* [[QA:Testcase_ABRT_Logger]] - Logger plugin
 
* [[QA:Testcase_ABRT_Logger]] - Logger plugin
Line 111: Line 57:
 
* [[QA:Testcase ABRT Cron]] -- periodical plugins using cron
 
* [[QA:Testcase ABRT Cron]] -- periodical plugins using cron
 
* [[QA:Testcase ABRT Plugins]] -- configuring plugins
 
* [[QA:Testcase ABRT Plugins]] -- configuring plugins
 
[https://fedoraproject.org/wiki/Category:ABRT_Test_Cases  ABRT_Test_Cases] might have more TestCases in the future.
 
 
  
 
=== Known issues ===  
 
=== Known issues ===  
  
 
Consult list of [https://fedorahosted.org/abrt/report/1 active tickets] before reporting an issue.  The most common issues are listed below:
 
Consult list of [https://fedorahosted.org/abrt/report/1 active tickets] before reporting an issue.  The most common issues are listed below:
* '''Recreate Report for same crash''' - if you want to recreate a report of same crash, you have to remove ABRT's db and cache (rm -r /var/cache/abrt/*) and make a crash gain
+
* '''Recreate report for same crash''' - if you want to recreate a report of same crash, you have to remove ABRT's db and cache (<code>rm -r /var/cache/abrt/*</code>) and make a crash gain
 
* '''Nothing happened?''' - if it seems to do nothing, try to disable PGP checking and restart daemon
 
* '''Nothing happened?''' - if it seems to do nothing, try to disable PGP checking and restart daemon
 
* '''Graphical warnings''' - gui writes some gtk warnings
 
* '''Graphical warnings''' - gui writes some gtk warnings
 
* '''rpm %requires''' - it needs rpm >= 4.7.0-1
 
* '''rpm %requires''' - it needs rpm >= 4.7.0-1
* you cannot use abrt to catch crashes of OpenOffice, KDE and Java apps -- they are catching those crashes themselves.
+
* '''Cannot catch OpenOffice, KDE and Java''' - these applications have a built-in method for capturing failures
* '''if you're updating from version <= 0.0.5-6 make sure you remove /var/abrt/cache/abrt-db (we've changed the db fomrat and not yet implemented automatic updating mechanism)'''
+
* '''if you're updating from version <= 0.0.5-6''' - make sure you remove /var/abrt/cache/abrt-db (we've changed the db fomrat and not yet implemented automatic updating mechanism)'''
* '''GUI doesn't inform you about success of failure of a reporting.''' But you can find results in ABRT's db (default path /var/cache/abrt, it is sqlite3 db, table name is "abrt")
+
* '''GUI doesn't inform you about success of failure of a reporting.''' - But you can find results in ABRT's db (default path /var/cache/abrt, it is sqlite3 db, table name is "abrt")
  
 
== Test Results ==
 
== Test Results ==
 
<!-- 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.  For example: -->
 
  
 
=== Issues that were identified ===
 
=== Issues that were identified ===
  
{| border="1px"
+
{|  
|-style="color: white; background-color: #3074c2; font-weight: bold"
+
! Tester
| Tester || Description || Bug references
+
! Description  
 +
! Bug references
 
|-
 
|-
| [[User:FasUser]] || ..... || [http://bugzilla.redhat.com/show_bug.cgi?id=xxx #xxx]
+
| [[User:FasUser]]  
 +
| Brief description of the problem
 +
| {{bz|123456}}
 
|-
 
|-
 
|}
 
|}
Line 142: Line 86:
 
=== Things that work alright ===
 
=== Things that work alright ===
  
{| border="1px"
+
{|
|-style="color: white; background-color: #3074c2; font-weight: bold"
+
! Tester
| Tester || Description
+
! Description
 
|-
 
|-
| [[User:FasUser]] || ..............
+
| [[User:FasUser]]  
 +
| Brief description of the use case
 
|-
 
|-
 
|}
 
|}
 
 
{{admon/warning| TODO: some tools/scripts/icons for users to help with testing.  Let the user easily monitor what is going on, or give him some tools so he can test ABRT even without command line tools. Or is this a bad idea? Please help us with this!}}
 
 
{{admon/warning| TODO: should users during ABRT test day report bugs directly into [[Bugzilla]]? How can we delete all such "bugs" later if they will eat too much space? Or will we use another Bugzilla? Where? How? ? Who can help?}}
 
  
 
[[Category:Test Days]]
 
[[Category:Test Days]]
 
[[Category:Draft_documentation]]
 

Revision as of 01:09, 18 August 2009

DATE TIME WHERE
2009-08-20 From 12:00 to 21:00 UTC (8am - 5pm EDT, 14:00 - 23:00 CET) #fedora-qa (webirc)

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 people will be available for testing, workarounds, bug fixes, and general discussion:

What's needed to test

  • A system with some kind of network connection
  • Rawhide (tips on installing Rawhide below), or the live CD available for this test day (again see below).
  • Your hardware profile uploaded to Smolt according to these instructions

How to test?

Update your machine

See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live Image

Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Architecture SHA256
[FIXME i686] FIXME
[FIXME x86-64] FIXME

Test Cases

Follow each of following Category:ABRT_Test_Cases and report your findings in the tables below.

Known issues

Consult list of active tickets before reporting an issue. The most common issues are listed below:

  • Recreate report for same crash - if you want to recreate a report of same crash, you have to remove ABRT's db and cache (rm -r /var/cache/abrt/*) and make a crash gain
  • Nothing happened? - if it seems to do nothing, try to disable PGP checking and restart daemon
  • Graphical warnings - gui writes some gtk warnings
  • rpm %requires - it needs rpm >= 4.7.0-1
  • Cannot catch OpenOffice, KDE and Java - these applications have a built-in method for capturing failures
  • if you're updating from version <= 0.0.5-6 - make sure you remove /var/abrt/cache/abrt-db (we've changed the db fomrat and not yet implemented automatic updating mechanism)
  • GUI doesn't inform you about success of failure of a reporting. - But you can find results in ABRT's db (default path /var/cache/abrt, it is sqlite3 db, table name is "abrt")

Test Results

Issues that were identified

Tester Description Bug references
User:FasUser Brief description of the problem RHBZ #123456

Things that work alright

Tester Description
User:FasUser Brief description of the use case