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 1: Line 1:
{{Infobox_group
{{Infobox_group
| name = Fedora Test Days
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_17_test_days]]
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_16_test_days]]
| caption = [[Features/ABRT|ABRT]] & [[Features/ABRTBacktraceDeduplication|Backtrace Deduplication]]
| caption = [[FIXME|FIXME]]
| date = 2012-04-26
| date = <<FIXME>>
| time = all day
| time = all day
| website = [[QA/Fedora_17_test_days]]
| website = [[QA/Fedora_17_test_days]]
Line 14: Line 14:
== What to test? ==
== What to test? ==


Today's instalment of Fedora Test Day will focus on '''Automated Bug Reporting Tool ([[Features/ABRT|ABRT]])''' and '''[[Features/ABRTBacktraceDeduplication|Backtrace Deduplication]] service'''
Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''


== Who's available ==
== Who's available ==


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:Jmoskovc|Jiří Moskovčák]] (jmoskovc), [[User:Npajkovs|Nikola Pajkovsky]] (npajkovs), [[User:dvlasenk|Denys Vlasenko]] (dvlasenk), [[User:Kklic|Karel Klíč]] (kklic), [[User:Mtoman|Michal Toman]] (mtoman), [[User:Mlichvar|Miroslav Lichvár]] (mlichvar), [[User:Mmilata|Martin Milata]] (mmilata), [[User:Jfilak|Jakub Filák]] (jfilak)
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
* Quality Assurance - [[User:Rmarko|Richard Marko]] (rmarko), [[User:Mnowak|Michal Nowak]]
* 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 ==  


* Physical machine or a virtual machine
List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
* Fedora 17 TC1 [http://dl.fedoraproject.org/pub/alt/stage/17.TC1/] or an updated [http://alt.fedoraproject.org/pub/alt/nightly-composes/ Fedora 17 pre-release]


=== How to test? ===
* Usb key
* Usb externally connected HD IDE/SATA
* Empty HD IDE/SATA/SCSI
* Free space on HD


==== '''Update your machine''' ====
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:


If you're running Fedora 17, make sure you have all the current updates for it installed, using the update manager.
* 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]
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]


==== '''Live image''' ====
== How to test? ==


You may download a non-destructive Fedora 17 live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]].
High level details on how a contributor can get involved. This can include (but not limited to):


Download the [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly Fedora 17 build] for your architecture (choose the desktop spin).
* 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''' ===
abrt-2.0.10-1.fc17
libreport-2.0.10-2.fc17
- in case these are not available in the official repo, Download them from Koji: [http://koji.fedoraproject.org/koji/packageinfo?packageID=7861 abrt] [http://koji.fedoraproject.org/koji/packageinfo?packageID=12092 libreport]


Use the following command to install/udpate all of them:
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:
  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


=== '''Live image''' ===


Make sure '''abrtd''' and '''abrt-ccpp''' services are running:
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].
<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>


==== Testing ====
== Test Cases ==


Follow each of these 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]].
# [[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 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.}}
== Test Results ==


{{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.}}
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:


=== 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=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=17&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=17&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
! User
! [[QA:Testcase_ABRT|Basic test]]
! Smolt Profile
! [[QA:Testcase_ABRT_Logger|Logger reporting]]
! [[QA:Testcase_sample_1|Sample test 1]]
! [[QA:Testcase_ABRT_Bugzilla|Bugzilla reporting]]
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_ABRT_Mailx|Mailx plugin]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase ABRT CLI|CLI interface]]
! [[QA:Testcase_sample_4|Sample test 4]]
! [[QA:Testcase ABRT kernel|Kernel oops]]
! [[QA:Testcase ABRT python|Python crash]]
! [[QA:Testcase ABRT vmcore|Kernel panic(vmcore)]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
| {{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|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| {{result|inprogress}}
| <references/>
|-
| [[User:Rmarko]]
| {{result|pass||816186}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail||816230}}<ref>No crash record in /var/crash/</ref>
| <references/>
|-
| [[User:mnowak|Michal Nowak]]
| {{result|pass||816595|816617}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass||816607}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail}}
| <references/>
|}
==== Integration test cases ====
{|
! User
! [[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}}
| <references/>
|-
| [[User:Rmarko]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| <references/>
| <references/>
|-
|-
| [[User:mnowak|Michal Nowak]]
| {{result|pass}}
| {{result|pass||816628}}
| {{result|pass}}
| {{result|pass}}
| <references/>
|}
|}


 
[[Category:Test Days]]
 
[[Category:QA Templates]]
 
[[Category:Fedora 17 Test Days|a]]
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)