From Fedora Project Wiki

No edit summary
(Updating the template)
Line 1: Line 1:
{{autolang|base=yes}}
{{Infobox_group
{{Infobox_group
| name = Fedora Test Days
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_16_test_days]]
| caption = [[Features/ABRT|ABRT]] & [[Features/Unified_Problem_Reporting_UI|libreport]]
| caption = [[Features/ABRT|ABRT]] & [[Features/Unified_Problem_Reporting_UI|libreport]]
| date = 2011-09-20
| date = 2011-09-20
Line 12: Line 13:
{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
{{admon/note | 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 [http://bugzilla.redhat.com 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}


== What to test? ==
=== What to test? ===


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


== Who's available ==
=== Who's available ===


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:jmoskovc|Jiří Moskovčák]] (jmoskovc)
* Development - Jiří Moskovčák (jmoskovc), Nikola Pajkovsky (npajkovs), Denys Vlasenko (dvlasenk), Karel Klíč (kklic), Michal Toman (mtoman)
* Quality Assurance - [[User:Rmarko|Richard Marko]] (rmarko), [[User:mnowak|Michal Nowak]] (mnowak)
* Quality Assurance - [[User:Rmarko|Richard Marko]] (rmarko), [[User:mnowak|Michal Nowak]] (mnowak)




== What's needed to test ==
=== Prerequisite for Test Day ===  


* Physical machine or a virtual machine
* Physical machine or a virtual machine
* An updated [http://alt.fedoraproject.org/pub/alt/nightly-composes/ Fedora 16 pre-release], or the special live image (see [[Test Day:2011-09-01_Intel#Live_image|below]])
* An updated [http://alt.fedoraproject.org/pub/alt/nightly-composes/ Fedora 16 pre-release], or the special live image (see [[Test Day:2011-09-01_Intel#Live_image|below]])


== How to test? ==
=== How to test? ===


=== '''Update your machine''' ===
==== '''Update your machine''' ====


If you're running Fedora 16, make sure you have all the current updates for it installed, using the update manager. Or you can use a live image:
If you're running Fedora 16, make sure you have all the current updates for it installed, using the update manager. Or you can use a live image:


=== '''Live image''' ===
==== '''Live image''' ====


Optionally, you may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
Optionally, you may download a non-destructive Fedora 16 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
Line 71: Line 72:
   yum -y install 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
   yum -y install 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


=== Testing ===
==== Testing ====


Follow each of these test cases:  
Follow each of these test cases:  
Line 88: Line 89:
# [[QA:Testcase ABRT python]] - python tracebacks
# [[QA:Testcase ABRT python]] - python tracebacks


== Test Results ==
{{admon/important|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.}}
 
{{admon/note|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 [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=16&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=16&component=libreport 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=16&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=16&component=libreport 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 [[Template:result|result template]] to enter your result, as shown in the example result line.

Revision as of 10:00, 21 September 2011

Fedora Test Days
}}}
ABRT & libreport
Date 2011-09-20
Time all day
Website ABRT homepage
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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), Michal Nowak (mnowak)


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. Or you can use a live image:

Live image

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

Architecture SHA256SUM
i686 1d235e29f013db7d85277086a3eb11be81a8b690ddcd16c5f46d2dfbcdd12b83
x86_64 bdb309a42f99ba1c6221c85912960e4aebe82596fdd2d9027a41f16275d6fa74


In particular, you should have the following packages installed:

  • abrt
  • abrt-cli
  • abrt-gui
  • abrt-libs
  • abrt-desktop
  • abrt-addon-ccpp
  • abrt-addon-python
  • abrt-addon-kerneloops
  • libreport
  • libreport-cli
  • libreport-gtk
  • libreport-newt
  • libreport-python
  • libreport-plugin-mailx
  • libreport-plugin-logger
  • libreport-plugin-bugzilla
  • libreport-plugin-kerneloops
  • libreport-plugin-reportuploader

Use following command to install/udpate all of them: 

 yum -y install 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

Testing

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 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
Important.png
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.
Note.png
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 Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User
Pass pass
none
Warning warn
[1]
Fail fail
[2]
  1. ↑ Test pass, but also encountered RHBZ #54321
  2. ↑ RHBZ #12345
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2011-09-20_ABRT&oldid=253968"