From Fedora Project Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
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:jfilak|Jakub Filák]] (jfilak), [[User:mbrysa|Marek Bryša]] (mbrysa), [[User:mhabrnal|Matěj Habrnál]] (mhabrnal), [[User:rmarko|Richard Marko]] (impure_hate)
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
* Quality Assurance - ??
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  


List any prerequisite needs for the test event.
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
* Usb key
* 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]
* Usb externally connected HD IDE/SATA
* Empty HD IDE/SATA/SCSI
* Free space on HD


== How to test? ==
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:


=== '''Update your machine''' ===
* 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]


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:
== How to test? ==


=== '''Live image''' ===
High level details on how a contributor can get involved.  This can include (but not limited to):


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].
* Areas to target with exploratory testing
* A list of pre-defined test cases to execute
* How to report back results


=== Get latest abrt/libreport packages  ===
Here's another common chunk (again, replace XX as above):


The latest versions are:
=== '''Update your machine''' ===


  satyr-0.16-1.fc22
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:
  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:
=== '''Live image''' ===


  dnf -y install --enablerepo=updates-testing \
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].
  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 ==
== Test Cases ==


=== New and important features ===
Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
# [[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 ===
== Test Results ==


# [[QA:Testcase_ABRT]] - Basic test
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:
# [[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.
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
! Hardware
! [[QA:Testcase_sample_1|Sample test 1]]
! [[QA:Testcase ABRT ccpp-journal]] - systemd-coredump
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase ABRT containers]] - containers
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase ABRT Desktop auto-reporting]] - Desktop auto-reporting
! [[QA:Testcase_sample_4|Sample test 4]]
! [[QA:Testcase ABRT Application restart]] - Restart crashed application
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| KVM/Qemu
| {{result|none}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{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|pass}}
| {{result|none}}
| {{result|pass}}
| {{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.<ref>{{bz|1211941}}</ref><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/>
| <references/>
|-
|-
|}
|}


 
[[Category:QA Templates]]
[[Category:Fedora 22 Test Days]]
Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 4.0 International (see Fedora Project Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please solve the following task below and enter the answer in the box (more info):

Cancel Editing help (opens in new window)