(Drop integration tests (mostly obsolete or redundant)) |
|||
Line 121: | Line 121: | ||
# [[QA:Testcase ABRT vmcore]] - kernel oops | # [[QA:Testcase ABRT vmcore]] - kernel oops | ||
# [[QA:Testcase ABRT cnotify]] - console notification | # [[QA:Testcase ABRT cnotify]] - console notification | ||
{{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/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.}} | ||
Line 189: | Line 181: | ||
| {{result|inprogress}} | | {{result|inprogress}} | ||
| {{result|inprogress}} | | {{result|inprogress}} | ||
| {{result|inprogress}} | | {{result|inprogress}} | ||
| {{result|inprogress}} | | {{result|inprogress}} |
Revision as of 14:38, 6 May 2013
Fedora Test Days | |
---|---|
[ABRT & libreport] | |
Date | 2013-05-07 |
Time | 6:00 UTC - 16:00 UTC |
Website | ABRT homepage |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's instalment of Fedora Test Day will focus on:
- Automated Bug Reporting Tool (ABRT)
- Unified Problem Reporting UI (libreport)
- Simplified crash reporting via ABRT Server (Fedora 18 Feature)
- Gnome-abrt
- SEAlert integration
- Tainted kernel links
- abrt server UX
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Jiří Moskovčák (jmoskovc), Denys Vlasenko (dvlasenk), Michal Toman (mtoman), Richard Marko (rmarko), Filák Jakub (jfilak), Lichvár Miroslav (mlichvar)
- Quality Assurance - David Kutálek (dkutalek), Martin Kyral (mkyral)
Prerequisite for Test Day
- Physical machine or a virtual machine
- An updated Fedora 19 pre-release
How to test?
Update your machine
If you're running Fedora 19, make sure you have all the current updates for it installed, using the update manager.
Live image
You may download a non-destructive Fedora 19 live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
Architecture | SHA256SUM |
---|---|
x86_64 (version 2) | 2c2f2fa700f5fa73bc3f1ff382139a92107d246375c5287d39b84a307426bce8 |
i686 (version 2) | 6eeb906fde5548dc601063387083708656827ce875d2f1c0536e820bde3f5aa8 |
Get latest abrt/libreport packages
The latest versions are:
abrt-2.1.4-1.fc19
libreport-2.2.4-1.fc19
btparser-0.19-1.fc19
gnome-abrt-0.2.12-1.fc19
Use the following command to install/update all of them:
yum -y install --enablerepo=updates-testing \ abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-python abrt-addon-vmcore abrt-addon-xorg \ abrt-desktop abrt-dbus abrt-gui abrt-libs abrt-cli abrt-retrace-client abrt-plugin-bodhi abrt-tui \ libreport libreport-compat libreport-filesystem libreport-cli libreport-gtk libreport-newt libreport-web \ libreport-python libreport-plugin-mailx libreport-plugin-logger libreport-plugin-bugzilla \ libreport-plugin-kerneloops libreport-plugin-reportuploader libreport-plugin-rhtsupport libreport-plugin-ureport \ btparser btparser-python \ gnome-abrt elfutils
Make sure that:
- abrtd and abrt-ccpp services are running:
# systemctl start abrtd.service # systemctl status abrtd.service # systemctl start abrt-ccpp.service # systemctl status abrt-ccpp.service
- file
/proc/sys/kernel/core_pattern
contains following output:
# cat /proc/sys/kernel/core_pattern |/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e
Test Cases
For better orientation there are several groups of test cases, top priority first. Follow each of these test cases, or just some group(s) of them in case of limited time for testing.
New and important features
- QA:Testcase ABRT Reporting Known Crash - reporting of known crash
- QA:Testcase ABRT ruby gem - ruby exceptions
- QA:Testcase GNOME ABRT MAIN - gnome-abrt
- QA:Testcase ABRT Configuration Storage - configuration storage
- QA:Testcase ABRT SELinux - ABRT GUI now catches AVC messages, too
- QA:Testcase ABRT Knowledgebase - ABRT provides more information about common problems
- QA:Testcase ABRT server - ABRT server user experience
Basic functionality
- QA:Testcase_ABRT - Basic test
- QA:Testcase_ABRT_Logger - Logger plugin
- QA:Testcase_ABRT_Bugzilla - Bugzilla plugin
- QA:Testcase_ABRT_Mailx - Mailx plugin
- QA:Testcase ABRT CLI - CLI interface
- QA:Testcase ABRT kernel - kernel oops
- QA:Testcase ABRT python - python tracebacks
- QA:Testcase ABRT vmcore - kernel oops
- QA:Testcase ABRT cnotify - console notification
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, or btparser for backtrace parser related bugs, or gnome-abrt for new Gnome Abrt GUI. 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.
New and important features
User | Reporting known crash | Ruby exceptions | Gnome ABRT | Configuration storage | SELinux alerts | Knowledgebase | ABRT server user experience | References |
---|---|---|---|---|---|---|---|---|
Sample User |
Basic functionality
User | Basic test | Logger reporting | Bugzilla reporting | Mailx plugin | CLI interface | Kernel oops | Python crash | Kernel panic(vmcore) | References |
---|---|---|---|---|---|---|---|---|---|
Sample User |