Test Day:2012-10-01 ABRT: Difference between revisions

Revision as of 19:04, 29 August 2012

Fedora Test Days

FIXME

Date	<<FIXME>>
Time	all day

Website	QA/Fedora_18_test_days
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), Denys Vlasenko (dvlasenk), Karel Klíč (kklic), Michal Toman (mtoman)
Quality Assurance - David Kutalek (dkutalek), Richard Marko (rmarko), Martin Kyral (mkyral)

Prerequisite for Test Day

Physical machine or a virtual machine
An updated Fedora 18 pre-release

How to test?

Update your machine

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

Live image

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

Download the nightly Fedora 18 build for your architecture. Choose the mainstream 'desktop' spin or any other desktop-like spin (kde, lxde, xfce).

Get latest abrt/libreport packages

The latest versions are (FIXME):

abrt-2.0.12-1.fc18
libreport-2.0.13-1.fc18
btparser-0.18-2.fc18

Use the following command to install/update all of them (FIXME):

yum -y install --enablerepo=updates-testing \
  abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-python abrt-desktop \
  abrt-gui abrt-libs abrt-cli abrt-retrace-client \
  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 that:

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 %s %c %p %u %g %t e

To be able to use the retrace server feature you have to edit the configuration and change its URL to retrace02.fedoraproject.org. To do so, open abrt-gui and go to Edit->Preferences->Retrace Server and change the URL to retrace02.fedoraproject.org and write insecure to insecure option entry.

Temporary retrace server
As this is only a temporary state and insecure option is required for the second server to work it's not a good idea to use coredumps that may contain sensitive data. The second server will replace main server soon.

FIXME: probably just sensitive data warning?

Test Cases

Follow each of these test cases (FIXME):

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 CLI - CLI interface
QA:Testcase ABRT kernel - kernel oops
QA:Testcase ABRT vmcore - kernel oops
QA:Testcase ABRT python - python tracebacks
QA:Testcase Libreport sealert - sealert integration
QA:Testcase Libreport anaconda - anaconda integration
QA:Testcase Libreport firstboot - firstboot integration
QA:Testcase Retrace Server CLI - Retrace Server CLI
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.

Abrt test cases

User	Basic test	Logger reporting	Bugzilla reporting	Mailx plugin	CLI interface	Kernel oops	Python crash	Kernel panic(vmcore)	References
Sample User	pass	warn ^[1]	fail ^[2]	inprogress	inprogress	inprogress	inprogress	inprogress	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345

Integration test cases

User	sealert	anaconda	firstboot	Retrace cli	Retrace gui	References
Sample User	inprogress	inprogress	inprogress	inprogress	inprogress

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

[2] RHBZ #12345

[1]

[2]

@@ Line 14: / Line 14: @@
 == What to test? ==
-Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
+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 ==
 The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
-* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+* Development - Jiří Moskovčák (jmoskovc), Denys Vlasenko (dvlasenk), Karel Klíč (kklic), Michal Toman (mtoman)
-* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
+* Quality Assurance - [[User:dkutalek|David Kutalek]] (dkutalek), [[User:Rmarko|Richard Marko]] (rmarko), Martin Kyral (mkyral)
 == Prerequisite for Test Day ==
-List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+* Physical machine or a virtual machine
+* An updated [http://alt.fedoraproject.org/pub/alt/nightly-composes/ Fedora 18 pre-release]
-* Usb key
+== How to test? ==
-* Usb externally connected HD IDE/SATA
-* Empty HD IDE/SATA/SCSI
+=== '''Update your machine''' ===
-* Free space on HD
+If you're running Fedora 18, make sure you have all the current updates for it installed, using the update manager.
+=== '''Live image''' ===
-Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
+You may download a non-destructive Fedora 18 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
-* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
+Download the [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly Fedora 18 build] for your architecture. Choose the mainstream 'desktop' spin or any other desktop-like spin (kde, lxde, xfce).
-* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
-== How to test? ==
+==== '''Get latest abrt/libreport packages''' ====
-High level details on how a contributor can get involved.  This can include (but not limited to):
+The latest versions are (FIXME):
-* Areas to target with exploratory testing
+abrt-2.0.12-1.fc18<br/>
-* A list of pre-defined test cases to execute
+libreport-2.0.13-1.fc18<br/>
-* How to report back results
+btparser-0.18-2.fc18
-Here's another common chunk (again, replace XX as above):
+Use the following command to install/update all of them (FIXME):
-=== '''Update your machine''' ===
+<pre>
+yum -y install --enablerepo=updates-testing \
+  abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-python abrt-desktop \
+  abrt-gui abrt-libs abrt-cli abrt-retrace-client \
+  libreport libreport-cli libreport-gtk libreport-newt libreport-python \
+  libreport-plugin-mailx libreport-plugin-logger libreport-plugin-bugzilla \
+  libreport-plugin-kerneloops libreport-plugin-reportuploader
+</pre>
-If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+Make sure that:
+* '''abrtd''' and '''abrt-ccpp''' services are running:
+<pre>
+# service abrtd start
+Starting abrtd (via systemctl):                            [  OK  ]
+# service abrt-ccpp start
+Starting abrt-ccpp (via systemctl):                        [  OK  ]
+</pre>
+* file {{filename|/proc/sys/kernel/core_pattern}} contains following output:
+<pre>
+# cat /proc/sys/kernel/core_pattern
+|/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e
+</pre>
-=== '''Live image''' ===
+<strike>To be able to use the retrace server feature you have to edit the configuration and change its URL to {{command|retrace02.fedoraproject.org}}. To do so, open {{command|abrt-gui}} and go to ''Edit->Preferences->Retrace Server'' and change the URL to {{command|retrace02.fedoraproject.org}} and write '''insecure''' to insecure option entry.
-Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+{{admon/warning|Temporary retrace server|As this is only a temporary state and '''insecure''' option is required for the second server to work it's not a good idea to use coredumps that may contain sensitive data. The second server will replace main server soon.}}
+</strike> FIXME: probably just sensitive data warning?
 == Test Cases ==
-Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
+Follow each of these test cases (FIXME):
+# [[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 CLI]] - CLI interface
+# [[QA:Testcase ABRT kernel]] - kernel oops
+# [[QA:Testcase ABRT vmcore]] - kernel oops
+# [[QA:Testcase ABRT python]] - python tracebacks
+# [[QA:Testcase Libreport sealert]] - sealert integration
+# [[QA:Testcase Libreport anaconda]] - anaconda integration
+# [[QA:Testcase Libreport firstboot]] - firstboot integration
+# [[QA:Testcase Retrace Server CLI]] - Retrace Server CLI
+# [[QA:Testcase Retrace Server GUI]] - Retrace Server in ABRT GUI
+{{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 ==
-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 some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
-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=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. 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, and the second should be a link to the Smolt profile of the system you tested. 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.
+==== Abrt test cases ====
 {|
 ! User
-! Smolt Profile
+! [[QA:Testcase_ABRT|Basic test]]
-! [[QA:Testcase_sample_1|Sample test 1]]
+! [[QA:Testcase_ABRT_Logger|Logger reporting]]
-! [[QA:Testcase_sample_2|Sample test 2]]
+! [[QA:Testcase_ABRT_Bugzilla|Bugzilla reporting]]
-! [[QA:Testcase_sample_3|Sample test 3]]
+! [[QA:Testcase_ABRT_Mailx|Mailx plugin]]
-! [[QA:Testcase_sample_4|Sample test 4]]
+! [[QA:Testcase ABRT CLI|CLI interface]]
+! [[QA:Testcase ABRT kernel|Kernel oops]]
+! [[QA:Testcase ABRT python|Python crash]]
+! [[QA:Testcase ABRT vmcore|Kernel panic(vmcore)]]
 ! References
 |-
 | [[User:SampleUser|Sample User]]
-| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
-| {{result|none}}
 | {{result|pass}}
 | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 | {{result|fail}} <ref>{{bz|12345}}</ref>
+| {{result|inprogress}}
+| {{result|inprogress}}
+| {{result|inprogress}}
+| {{result|inprogress}}
+| {{result|inprogress}}
+| <references/>
+|-
+|}
+==== Integration test cases ====
+{|
+! User
+! [[QA:Testcase Libreport sealert|sealert]]
+! [[QA:Testcase Libreport anaconda|anaconda]]
+! [[QA:Testcase Libreport firstboot|firstboot]]
+! [[QA:Testcase Retrace Server CLI|Retrace cli]]
+! [[QA:Testcase Retrace Server GUI|Retrace gui]]
+! References
+|-
+| [[User:SampleUser|Sample User]]
+| {{result|inprogress}}
+| {{result|inprogress}}
+| {{result|inprogress}}
+| {{result|inprogress}}
+| {{result|inprogress}}
 | <references/>
 |-
@@ Line 84: / Line 153: @@
 [[Category:Test Days]]
-[[Category:QA Templates]]

Search