From Fedora Project Wiki

(Created page with "{{Infobox_group | name = Fedora Test Days | image = link=QA/Fedora_22_test_days | caption = ABRT | date = 2015-04-14 | time = all day | website ...")
 
Line 19: Line 19:
  
 
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:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+
* Development - [[User:jfilak|Jakub Filák]] (jfilak), [[User:mbrysa|Marek Brýša]] (mbrysa), [[User:mhabrnal|Matěj Habrnál]] (mhabrnal), [[User:rmarko|Richard Marko]] (impure_hate)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
+
* Quality Assurance - ??
  
 
== Prerequisite for Test Day ==  
 
== 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?
+
List any prerequisite needs for the test event.
  
* Usb key
+
* Physical machine or a virtual machine
* Usb externally connected HD IDE/SATA
+
* An updated [http://fedoraproject.org/get-prerelease Fedora 22 pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
* Empty HD IDE/SATA/SCSI
 
* Free space on HD
 
  
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
+
== How to test? ==
  
* 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]
+
=== '''Update your machine''' ===
  
== How to test? ==
+
If you're running Fedora 22, 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:
 +
 
 +
=== '''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]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
 +
 
 +
=== 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:
  
* Areas to target with exploratory testing
+
  satyr-0.16-1.fc22
* A list of pre-defined test cases to execute
+
  libreport-2.5.1-1.fc22
* How to report back results
+
  abrt-2.5.1-1.fc22
 +
  gnome-abrt-1.1.1-1.fc22
  
Here's another common chunk (again, replace XX as above):
+
Use the following command to install/update all of them:
  
=== '''Update your machine''' ===
+
  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 \
 +
  satyr gnome-abrt
  
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:
+
If these packages are not available in the official Fedora 22 repositories yet, please enable this COPR repository and run the command above:
 +
https://copr.fedoraproject.org/coprs/jfilak/abrt-test-day/
  
=== '''Live image''' ===
+
Make sure that:
 +
* '''abrtd''' and '''abrt-ccpp''' services are running:
 +
<pre>
 +
# systemctl start abrtd.service
 +
# systemctl status abrtd.service
  
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].
+
# systemctl start abrt-ccpp.service
 +
# systemctl status abrt-ccpp.service
 +
</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>
  
 
== Test Cases ==
 
== 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]].
+
=== New and important features ===
 +
 
 +
 
 +
=== 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
 +
# [[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
  
 
== 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. 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=22&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=22&component=gnome-abrt gnome-abrt] for bugs in the ABRT 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. 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=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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
 
  
 
{|
 
{|
 
! User
 
! User
! [[QA:Testcase_sample_1|Sample test 1]]
+
! Hardware
! [[QA:Testcase_sample_2|Sample test 2]]
+
! [[QA:Testcase_ABRT_Reporting_Known_Crash|Reporting known crash]]
! [[QA:Testcase_sample_3|Sample test 3]]
+
! [[QA:Testcase ABRT ruby gem|Ruby exceptions]]
! [[QA:Testcase_sample_4|Sample test 4]]
+
! [[QA:Testcase GNOME ABRT MAIN|Gnome ABRT]]
 +
! [[QA:Testcase_ABRT_Configuration_Storage|Configuration storage]]
 +
! [[QA:Testcase_ABRT_SELinux|SELinux alerts]]
 +
! [[QA:Testcase ABRT Knowledgebase|Knowledgebase]]
 +
! [[QA:Testcase_ABRT_server|ABRT server user experience]]
 
! References
 
! References
 
|-
 
|-
 
| [[User:SampleUser|Sample User]]
 
| [[User:SampleUser|Sample User]]
 +
| KVM/Qemu
 
| {{result|none}}  
 
| {{result|none}}  
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 
| <references/>
 
| <references/>
 
|-
 
|-

Revision as of 09:17, 9 April 2015

Fedora Test Days
Echo-testing-48px.png
ABRT

Date 2015-04-14
Time all day

Website QA/Fedora_22_test_days
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 ABRT

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

List any prerequisite needs for the test event.

How to test?

Update your machine

If you're running Fedora 22, 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 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. Live images can be found here.

Get latest abrt/libreport packages

The latest versions are:

 satyr-0.16-1.fc22
 libreport-2.5.1-1.fc22
 abrt-2.5.1-1.fc22
 gnome-abrt-1.1.1-1.fc22

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 \
 satyr gnome-abrt

If these packages are not available in the official Fedora 22 repositories yet, please enable this COPR repository and run the command above: https://copr.fedoraproject.org/coprs/jfilak/abrt-test-day/

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

New and important features

Basic functionality

  1. QA:Testcase_ABRT - Basic test
  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 ABRT vmcore - kernel oops
  9. QA:Testcase ABRT cnotify - console notification
  10. QA:Testcase ABRT Reporting Known Crash - reporting of known crash
  11. QA:Testcase ABRT ruby gem - ruby exceptions
  12. QA:Testcase GNOME ABRT MAIN - gnome-abrt
  13. QA:Testcase ABRT Configuration Storage - configuration storage
  14. QA:Testcase ABRT SELinux - ABRT GUI now catches AVC messages, too
  15. QA:Testcase ABRT Knowledgebase - ABRT provides more information about common problems
  16. QA:Testcase ABRT server - ABRT server user experience

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component abrt, or gnome-abrt for bugs in the ABRT 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. For each test case, use the result template to enter your result, as shown in the example result line.

User Hardware Reporting known crash Ruby exceptions Gnome ABRT Configuration storage SELinux alerts Knowledgebase ABRT server user experience References
Sample User KVM/Qemu
none
Pass pass
Warning warn
[1]
Fail fail
[2]
Pass pass
Pass pass
Pass pass
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345