From Fedora Project Wiki

Revision as of 20:51, 24 September 2011 by Mtoman (talk | contribs) (Add Retrace server test cases)

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
Fedora Test Days
ABRT & libreport

Date 2011-09-26
Time all day

Website ABRT homepage
IRC #fedora-test-day (webirc)
Mailing list test

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on Automated Bug Reporting Tool (ABRT) and Unified Problem Reporting UI (libreport).

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), Michal Toman (mtoman)
  • Quality Assurance - Richard Marko (rmarko)

Prerequisite for Test Day

How to test?

Update your machine

If you're running Fedora 16, make sure you have all the current updates for it installed, using the update manager.

Live image

You may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.

Download the nightly Fedora 16 build for your architecture (choose the desktop spin).

Get latest abrt/libreport packages

Use the following command to install/udpate all of them:

 yum -y install --enablerepo=updates-testing abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-python abrt-desktop abrt-gui abrt-libs abrt-cli libreport libreport-cli libreport-gtk libreport-newt libreport-python libreport-plugin-mailx libreport-plugin-logger libreport-plugin-bugzilla libreport-plugin-kerneloops libreport-plugin-reportuploader

Make sure abrtd and abrt-ccpp services are running:

# service abrtd start
Starting abrtd (via systemctl):                            [  OK  ]
# service abrt-ccpp start
Starting abrt-ccpp (via systemctl):                        [  OK  ]
  • File /proc/sys/kernel/core_pattern contains following output:
# cat /proc/sys/kernel/core_pattern
|/usr/libexec/abrt-hook-ccpp /var/spool/abrt %s %c %p %u %g %t %h %e 636f726500


Follow each of these test cases:

  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 CLI - CLI interface
  6. QA:Testcase ABRT kernel - kernel oops
  7. QA:Testcase ABRT python - python tracebacks
  8. QA:Testcase Libreport sealert - sealert integration
  9. QA:Testcase Libreport anaconda - anaconda integration
  10. QA:Testcase Libreport firstboot - firstboot integration
  11. QA:Testcase Retrace Server CLI - Retrace Server CLI
  12. QA:Testcase Retrace Server GUI - Retrace Server in ABRT GUI
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.
Report SELinux denials against ABRT
If you encounter some SELinux (AVC) denials during testing, please report them against the abrt package, not selinux package. Thanks.

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component abrt, or libreport for bugs in the libreport library. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

User Basic test Logger reporting Bugzilla reporting Mailx plugin CLI interface Kernel oops Python crash sealert anaconda firstboot References
Sample User
Pass pass
Warning warn
Fail fail
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
Inprogress inprogress
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345