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 save the changes below to finish undoing the edit.

Latest revision Your text
Line 20: Line 20:
 
* '''Automated Bug Reporting Tool ([https://fedorahosted.org/abrt ABRT])'''  
 
* '''Automated Bug Reporting Tool ([https://fedorahosted.org/abrt ABRT])'''  
 
* '''Unified Problem Reporting UI ([[Features/Unified Problem Reporting UI|libreport]])'''
 
* '''Unified Problem Reporting UI ([[Features/Unified Problem Reporting UI|libreport]])'''
 +
* '''Simplified crash reporting via ABRT Server ([[Features/SimplifiedCrashReporting|Fedora 18 Feature]])'''
 
* '''Gnome-abrt'''
 
* '''Gnome-abrt'''
 
* '''SEAlert integration'''
 
* '''SEAlert integration'''
Line 49: Line 50:
 
! Architecture !! SHA256SUM  
 
! Architecture !! SHA256SUM  
 
|-  
 
|-  
| [http://fedorapeople.org/groups/qa/testday-20130507-3-x86_64.iso x86_64] (version 3) || 5b457aab4cdfdb42869eb5d500f8f96631286880afce158ef38397a13d16726e
+
| [http://fedorapeople.org/groups/qa/testday-20130507-x86_64.iso x86_64] (outdated) || 6277f319b43b05df164eed859554865e1f7304ca66004cd2bdd6ce962b9ce7d9
 
|-
 
|-
| [http://fedorapeople.org/groups/qa/testday-20130507-3-i686.iso i686] (version 3) || c044398025e7821cf59415753670de8cf9e1d27c720d87b1d369a9e47eb6f8cd
+
| [http://fedorapeople.org/groups/qa/testday-20130507-i686.iso i686] (outdated) || 25b0be65f391c941a36f3941bbde024836dee6161061487ceb7b39ad84974a58
 
|}
 
|}
  
Line 58: Line 59:
 
The latest versions are:
 
The latest versions are:
  
abrt-2.1.4-3.fc19<br/>
+
abrt-2.1.4-1.fc19<br/>
libreport-2.1.4-4.fc19<br/>
+
libreport-2.2.4-1.fc19<br/>
btparser-0.25-2.fc19<br>
+
btparser-0.19-1.fc19<br>
gnome-abrt-0.2.12-3.fc19
+
gnome-abrt-0.2.12-1.fc19
  
 
Use the following command to install/update all of them:
 
Use the following command to install/update all of them:
Line 97: Line 98:
  
 
For better orientation there are several groups of test cases, top priority first.
 
For better orientation there are several groups of test cases, top priority first.
Follow each of these test cases, or just some group(s) of them in case of limited time for testing.
+
Follow each of these test cases, or just some group(s) of them in case of limited time for testing.
  
 
=== New and important features ===
 
=== New and important features ===
  
 +
# [[Features/SimplifiedCrashReporting]] - Simplified Crash Reporting (F18 Feature)
 
# [[QA:Testcase ABRT Reporting Known Crash]] - reporting of known crash
 
# [[QA:Testcase ABRT Reporting Known Crash]] - reporting of known crash
 
# [[QA:Testcase ABRT ruby gem]] - ruby exceptions
 
# [[QA:Testcase ABRT ruby gem]] - ruby exceptions
Line 119: Line 121:
 
# [[QA:Testcase ABRT python]] - python tracebacks
 
# [[QA:Testcase ABRT python]] - python tracebacks
 
# [[QA:Testcase ABRT vmcore]] - kernel oops
 
# [[QA:Testcase ABRT vmcore]] - kernel oops
# [[QA:Testcase ABRT cnotify]] - console notification
+
 
 +
=== Integration ===
 +
 
 +
# [[QA:Testcase Libreport sealert]] - sealert integration
 +
# [[QA:Testcase Libreport anaconda]] - anaconda integration
 +
# [[QA:Testcase Libreport Anaconda Install]] - anaconda integration (directly in install)
 +
# [[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/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.}}
Line 133: Line 142:
 
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=18&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=libreport libreport] for bugs in the libreport library, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=btparser btparser] for backtrace parser related bugs, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=gnome-abrt gnome-abrt] for new Gnome Abrt GUI. 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=18&component=abrt abrt], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=libreport libreport] for bugs in the libreport library, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=btparser btparser] for backtrace parser related bugs, or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=18&component=gnome-abrt gnome-abrt] for new Gnome Abrt GUI. 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.
  
{{admon/note|Alternative reporting through the web application | If you are not familiar with the Wiki editing or you come here in prime time and there are a lot of conflicting edits in the Wiki, you can try to report your results via our web application. '''Results from this web application will be automatically transferred to the Wiki on 2013-05-21''' and the alternative reporting system will be shut down to this date. Feel free to continue testing and filling the wiki even after this date. Please note the number of reports currently visible in the wiki doesn't correspond to the number of reports sent so far (i.e. reports sent through the web application).}}
+
{{admon/important|Important workaround|As of now, abrt contains a bug which prevents it from working properly after booting from LiveCD. If you booted from the live image, please do ''systemctl restart abrtd'' as root before starting.}}
[http://autoqa-stg.fedoraproject.org/testdays/show_event?event_id=4 F19 ABRT Testday application]
 
 
 
{{admon/important|Enable the testing repository|To have the freshest available abrt build, please enable the test-day abrt repository by downloading [http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo fedora-abrt.repo] file and placing it in your /etc/yum.repos.d directory. This is important for the test day live image, as the image is missing some packages needed for some of the test cases and they are not present in the standard Fedora 19 repositories in the desired version. We aplologize for the inconvenience.}}
 
  
 
==== New and important features ====
 
==== New and important features ====
Line 142: Line 148:
 
{|
 
{|
 
! User
 
! User
! Hardware
+
! [[QA:Testcase_ABRT|Simplified crash reporting]]
! [[QA:Testcase_ABRT_Reporting_Known_Crash|Reporting known crash]]
+
! [[QA:Testcase_ABRT_Logger|Reporting known crash]]
 
! [[QA:Testcase ABRT ruby gem|Ruby exceptions]]
 
! [[QA:Testcase ABRT ruby gem|Ruby exceptions]]
 
! [[QA:Testcase GNOME ABRT MAIN|Gnome ABRT]]
 
! [[QA:Testcase GNOME ABRT MAIN|Gnome ABRT]]
 
! [[QA:Testcase_ABRT_Configuration_Storage|Configuration storage]]
 
! [[QA:Testcase_ABRT_Configuration_Storage|Configuration storage]]
 
! [[QA:Testcase_ABRT_SELinux|SELinux alerts]]
 
! [[QA:Testcase_ABRT_SELinux|SELinux alerts]]
! [[QA:Testcase ABRT Knowledgebase|Knowledgebase]]
+
! [[QA:Testcase_ABRT_tainted|Knowledgebase]]
! [[QA:Testcase_ABRT_server|ABRT server user experience]]
+
! [[QA:Testcase_ABRT_Srv_UX|ABRT server user experience]]
 
! References
 
! References
 
|-
 
|-
| [[User:mkyral|mkyral]]
+
| [[User:SampleUser|Sample User]]
| VirtualBox
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|fail}}  <ref>The same issue as jkejda - clicking Report brings sealert window up, but having all the fields empty (ie. unable to report anything at all)</ref>
 
| {{result|fail}}  <ref group="long">vlc crashes are taken as duplicate of the will_segfault crash. The bug is already known to the developers and is being fixed.
 
After cleaning the crash directories the test PASSes</ref>
 
|
 
| <references/>
 
|-
 
| [[User:jmoskovc|jmoskovc]]
 
| kvm
 
| {{result|pass}
 
| {{result|pass}}
 
| {{result|warn}}  <ref>Killing gnome-abrt produces an empty core_backtrace, the basic functionality of gnome-abrt works</ref>{{result|pass}}  <ref group="long">The gnome-abrt itself works, but I hit a problem when trying to kill gnome-abrt:
 
 
 
May  7 08:43:20 localhost abrtd: Directory 'ccpp-2013-05-07-08:43:19-1985' creation detected
 
May  7 08:43:20 localhost abrt[2174]: Saved core dump of pid 1985 (/usr/bin/python2.7) to /var/tmp/abrt/ccpp-2013-05-07-08:43:19-1985 (37634048 bytes)
 
May  7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2b: 1920/139723609384960
 
May  7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2c: 1920/139723609384960
 
May  7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2d: 1920/139723609384960
 
May  7 08:43:20 localhost abrtd: BDB2053 Freeing read locks for locker 0x2e: 1920/139723609384960
 
May  7 08:43:20 localhost abrtd: Generating core_backtrace
 
May  7 08:43:20 localhost abrtd: Generating backtrace
 
May  7 08:43:23 localhost abrtd: Backtrace is generated, 17605 bytes
 
May  7 08:43:24 localhost abrtd: Core backtrace is generated and saved, 0 bytes
 
May  7 08:43:26 localhost abrtd: Duplicate: core backtrace
 
May  7 08:43:26 localhost abrtd: DUP_OF_DIR: /var/tmp/abrt/ccpp-2013-05-07-07:50:47-1707
 
May  7 08:43:26 localhost abrtd: Deleting problem directory ccpp-2013-05-07-08:43:19-1985 (dup of ccpp-2013-05-07-07:50:47-1707)
 
</ref>
 
 
| {{result|pass}}
 
| {{result|pass}}
| {{result|fail}} <ref>AVC was visible in gnome-abrt, but setroubleshoot window was empty</ref>{{result|fail}} <ref group="long">gnome-abrt shows the AVC correctly, but the setroubleshoot window (which appears after clicking the report button) is empty and there is no AVC</ref>
+
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|pass}} 
+
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|pass}} 
+
| {{result|inprogress}}
| <references/>
+
| {{result|inprogress}}
|-
+
| {{result|inprogress}}
| [[User:lzachar|lzachar]]
+
| {{result|inprogress}}
| Lenovo T410
+
| {{result|inprogress}}
| {{result|pass}}
 
| {{result|pass}} 
 
| {{result|pass}} 
 
|
 
|
 
|
 
|
 
| <references/>
 
|-
 
| [[User:isenfeld|isenfeld]]
 
| Lenovo T420s
 
| {{result|pass}} 
 
| {{result|pass}} 
 
|
 
| {{result|pass}} 
 
| {{result|warn}}  <ref>Clicking on 'Report' didn't do anything for some reason. Should be tried again.</ref>
 
| {{result|pass}} 
 
|
 
| <references/>
 
|-
 
| [[User:mhradile|mhradile]]
 
| Virtual Manager
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|fail||960640|960647}}<ref>Also not all will_crashes were reported ;-) because it let me report this BZ#960625.</ref>
 
|
 
|
 
|
 
|
 
| <references/>
 
|-
 
| [[User:fholec|fholec]]
 
| VirtualBox
 
| {{result|pass}} 
 
|
 
|
 
|
 
|
 
|
 
|
 
| <references/>
 
|-
 
| [[User:fholec|fholec]]
 
| Lenovo IdeaPad S205
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|pass}}
 
|
 
| {{result|pass}}  <ref>VirtualBox downloaded different kernel as dependency -> not tested
 
 
 
VLC -> OK
 
 
 
Not able to install chrome, chromium, flash-plugin</ref>{{result|pass}} 
 
|
 
| <references/>
 
|-
 
| [[User:jkejda|jkejda]]
 
| VirtualBox
 
| {{result|pass}} 
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}  
 
| {{result|fail}} <ref>When you click on the 'Report' button SELinux Alert Browser start empty.</ref>
 
| {{result|pass}} 
 
| {{result|pass}}
 
 
| <references/>
 
| <references/>
 
|}
 
|}
Line 265: Line 174:
 
{|
 
{|
 
! User
 
! User
! Hardware
 
 
! [[QA:Testcase_ABRT|Basic test]]
 
! [[QA:Testcase_ABRT|Basic test]]
 
! [[QA:Testcase_ABRT_Logger|Logger reporting]]
 
! [[QA:Testcase_ABRT_Logger|Logger reporting]]
Line 274: Line 182:
 
! [[QA:Testcase ABRT python|Python crash]]
 
! [[QA:Testcase ABRT python|Python crash]]
 
! [[QA:Testcase ABRT vmcore|Kernel panic(vmcore)]]
 
! [[QA:Testcase ABRT vmcore|Kernel panic(vmcore)]]
! [[QA:Testcase_ABRT_cnotify|Console notification]]
 
 
! References
 
! References
 
|-
 
|-
| [[User:mkyral|mkyral]]
+
| [[User:SampleUser|Sample User]]
| VirtualBox
+
| {{result|pass}}
| {{result|pass}}
+
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|pass}}
+
| {{result|fail}} <ref>{{bz|12345}}</ref>
|  
+
| {{result|inprogress}}
|  
+
| {{result|inprogress}}
|  
+
| {{result|inprogress}}
|  
+
| {{result|inprogress}}
|  
+
| {{result|inprogress}}
| {{result|warn}} <ref group="long">crashkernel does not work at all (BZ#959914), tested notification only.
 
 
 
notification was not shown, vmcore was listed in the problems after clicking 'All problems' and inserting root passwd.</ref>
 
| {{result|pass}}
 
 
| <references/>
 
| <references/>
|-
+
|}
| [[User:jmoskovc|jmoskovc]]
 
| kvm
 
| {{result|pass}
 
| {{result|pass}}  <ref>It's not very easy to use the logger, the UI (cli nor gui) doesn't offer any convenient way for it</ref>
 
| {{result|pass}} 
 
| {{result|fail}}  <ref group="long">[liveuser@localhost ccpp-2013-05-07-10:08:18-2864]$ report-cli -e report_Mailx -- .
 
Mailx Recipient: jmoskovc@redhat.com
 
Mailx Sender: jmoskovc@redhat.com
 
  
No changes were detected in the report
+
==== Integration ====
Sending an email...
 
/usr/sbin/sendmail: No such file or directory
 
. . . message not sent.
 
Error running '/bin/mailx'
 
('report_Mailx' exited with 1)
 
</ref>
 
| {{result|fail}}  <ref group="long">[liveuser@localhost abrt]$ abrt-cli rm /var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864
 
Can't remove directory '/var/tmp/abrt/ccpp-2013-05-07-10:08:18-2864': Permission denied
 
  
[liveuser@localhost abrt]$ ls -l
+
{|
total 8
+
! User
drwxrwx---. 2 liveuser abrt  40 May  7 10:57 ccpp-2013-05-07-10:08:18-2864
+
! [[QA:Testcase Libreport sealert|sealert]]
</ref>
+
! [[QA:Testcase Libreport anaconda|anaconda]]
| {{result|pass}} 
+
! [[QA:Testcase Libreport Anaconda Install|anaconda install]]
| {{result|pass}} 
+
! [[QA:Testcase Libreport firstboot|firstboot]]
| {{result|warn}}  <ref>didn't test</ref>
+
! [[QA:Testcase Retrace Server CLI|Retrace cli]]
| {{result|warn}}  <ref>Works, but prints errors on the first login:
+
! [[QA:Testcase Retrace Server GUI|Retrace gui]]
 
+
! References
https://github.com/abrt/abrt/issues/649</ref>
 
| <references/>
 
 
|-
 
|-
| [[User:mhradile|mhradile]]
+
| [[User:SampleUser|Sample User]]
| Virtual Manager
+
| {{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|pass}} 
 
|
 
|
 
|
 
| <references/>
 
|-
 
| [[User:fholec|fholec]]
 
| Lenovo IdeaPad S205
 
| {{result|pass}}
 
| {{result|pass}}
 
|
 
| {{result|pass}<ref>Mail not received, but reported as sent</ref>
 
| {{result|warn}} <ref>Not able to remove directory of issue while logged in as liveuser</ref>
 
| {{result|pass}} 
 
| {{result|pass}} 
 
|
 
| {{result|pass}} 
 
| <references/>
 
|-
 
| [[User:jkejda|jkejda]]
 
| VirtualBox
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|pass}} 
 
| {{result|warn}} <ref group="long">Before testing:
 
- install 'libreport-plugin-mailx' from http://repos.fedorapeople.org/repos/jfilak/abrt/fedora-abrt.repo
 
- install 'sendmail'
 
 
 
I still waiting for email =o/
 
</ref>
 
| {{result|fail}}  {{result|warn}} <ref group="long">Reporting work (abrt-cli report to bugzilla) but not for Logger. This test case is wrong, command for report to Logger is 'report-cli -e report_Logger DIR'</ref>
 
| {{result|pass}}
 
| {{result|pass}}
 
|
 
| {{result|pass}}
 
 
| <references/>
 
| <references/>
 
|}
 
|}
  
== Long comments ==
+
[[Category:Test Days]]
<references group="long" />
 
 
 
  [[Category:Fedora 19 Test Days]]
 

Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 3.0 Unported (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)