Editing Test Day:2015-04-14 ABRT

{{Infobox_group
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_test_days]]
| caption = ABRT
| date = 2015-04-14
| time = all day
| website = [[QA/Fedora_22_test_days]]
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
| fedora_mailing_list = test
}}

{{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? ==

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 ...
* Development - [[User:jfilak|Jakub Filák]] (jfilak), [[User:mbrysa|Marek Bryša]] (mbrysa), [[User:mhabrnal|Matěj Habrnál]] (mhabrnal), [[User:rmarko|Richard Marko]] (impure_hate)
* Quality Assurance - ??

== Prerequisite for Test Day == 

List any prerequisite needs for the test event.

* Physical machine or a virtual machine
* 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]

== 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 [[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  ===

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:

  dnf -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/

'''Install and configure your favourite MTA (either Sendmail or Postfix).'''

Make sure that:
* '''abrtd''' and '''abrt-ccpp''' services are running:
<pre>
# systemctl start abrtd.service
# systemctl status abrtd.service

# 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 %P %i
</pre>

== Test Cases ==

=== New and important features ===
# [[QA:Testcase ABRT ccpp-journal]] - systemd-coredump
# [[QA:Testcase ABRT containers]] - containers
# [[QA:Testcase ABRT Desktop auto-reporting]] - Desktop auto-reporting
# [[QA:Testcase ABRT Application restart]] - Restart crashed application

=== 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-journal]] - kernel oops from journald
# [[QA:Testcase ABRT python]] - python tracebacks
# [[QA:Testcase ABRT python3]] - python3 tracebacks
# [[QA:Testcase ABRT vmcore]] - kernel oops
# [[QA:Testcase ABRT ruby gem]] - ruby exceptions
# [[QA:Testcase ABRT cnotify]] - console notification
# [[QA:Testcase ABRT Reporting Known Crash]] - reporting of known crash
# [[QA:Testcase GNOME ABRT MAIN]] - gnome-abrt
# [[QA:Testcase ABRT Configuration Storage]] - configuration storage
# [[QA:Testcase ABRT server]] - ABRT server user experience

== 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=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.

{|
! User
! Hardware
! [[QA:Testcase ABRT ccpp-journal]] - systemd-coredump
! [[QA:Testcase ABRT containers]] - containers
! [[QA:Testcase ABRT Desktop auto-reporting]] - Desktop auto-reporting
! [[QA:Testcase ABRT Application restart]] - Restart crashed application
! References
|-
| [[User:SampleUser|Sample User]]
| KVM/Qemu
| {{result|pass}}
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|none}}
| {{result|warn}}
| <references/>
|-
| [[User:mbrysa|Marek Brysa]]
| VirtualBox
| {{result|pass}}
| {{result|pass}} docker_inspect empty<ref>{{bz|1194280}}</ref>
| {{result|none}}
| {{result|none}}
| <references/>
|-
| [[User:pschindl|Petr Schindler]]
| Lenovo ThinkPad T540p
| {{result|pass}}
| {{result|pass}} <ref>Tested with Permissive</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:mkyral|Martin Kyral]]
| VirtualBox
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|warn}}In GNOME the buttons are present only when in the bubble (which can be gone in few secs), not in the notification overview <ref>{{bz|1211690}}</ref><br>In KDE, there's no access at all to the notification after it is hidden.<br>abrt-applet crashing<ref>{{bz|1211644}}</ref>
| <references/>
|-
-
| [[User:wolfantec|Antonio Insuasti]]
| KVM/Qemu & Lenovo ThinkPad W530
| {{result|pass}}
| {{result|pass}} <ref> Test with Enforcing on Qemu and Permissive on W530</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:xmrbrz|Bruno R. Zanuzzo]]
| ASUS k45vm x86_64
| {{result|pass}}
| {{result|pass}} <ref> I did not find the "container_image" field in report using permissive mode (container and host) </ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:juliuxpigface|juliuxpigface]]
| KVM/Qemu x86_64
| {{result|pass}}
| {{result|none}}
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:mhabrnal|Matej Habrnal]]
| VirtualBox
| {{result|pass}}
| {{result|pass}} docker_inspect empty<ref>{{bz|1194280}}</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|}

[[Category:QA Templates]]