From Fedora Project Wiki

(Created page with '{{QA/Test_Case |description=This test case tests the functionality of the ABRT feature. |actions= # We will check that the ''abrt-cli'' works and provides meani...')
 
No edit summary
(14 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] feature.
 
|description=This test case tests the functionality of the ABRT command line interface.
 
|setup=
# If you are running through the set of ABRT test cases you probably have a bunch of crash reports in cache. If not, then crash some applications with the command {{command|kill -SIGSEGV (pid)}}. Make sure they are not applications containing important data!
# Make sure you have {{package||abrt-cli}} installed: {{command|su -c 'yum install abrt-cli'}}
|actions=
|actions=
# We will check that the ''abrt-cli'' works and provides meaningful information
# Run {{command|abrt-cli list}} to show unreported crashes
# After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing: <pre>kill -SIGSEGV (pid)</pre>
# Run {{command|abrt-cli list --full}} to show all crashes
# Mind ''abrt'' daemon is running
# Try crash reporting: run {{command|abrt-cli report <tt>DIR</tt>}} to report a crash to e.g. Logger
# First investigate them via ''abrt-gui'' -- which packages crashed, when, version, etc.
#* Select reporting using Logger
# Run <pre>abrt-cli --get-list-full</pre> in terminal
# Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report
# Run <pre>abrt-cli --get-list</pre>
# Run <pre>abrt-cli --report <uuid></pre> to report the crash
# Run <pre>abrt-cli --report-always <uuid></pre> to report the crash without confirming
# Run <pre>abrt-cli --delete <uuid></pre> to delete item with UUID <uuid>
|results=
|results=
# Option '''--get-list-full''' shows all crashes
# Option '''list''' shows all not-yet-reported crashes
# Option '''--get-list''' shows all not-yet-reported crashes
# Option '''list --full''' shows all crashes
# Option '''--report''' shows crash report and asks for confirmation before sending it
# Option '''report''' shows crash report and asks for confirmation before sending it
# Option '''--report-always''' sends crash report
#* ABRT asks you to choose one of the analyzer 'local GDB debugger' or 'retrace sever' and then analyzes the crash and creates a report. When the report is ready, {{command|abrt-cli}} opens a text editor with the content of the report. You can see what's being reported, and you are able to fill in instructions on how to reproduce the crash and other comments.
# Option '''--delete''' deletes crash with UUID <uuid>
#* You are asked if you want to execute some reporter plugins or not.
# Option '''rm''' deletes crash
}}
}}
[[Category:ABRT_Test_Cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 15:28, 23 September 2011

Description

This test case tests the functionality of the ABRT command line interface.

Setup

  1. If you are running through the set of ABRT test cases you probably have a bunch of crash reports in cache. If not, then crash some applications with the command kill -SIGSEGV (pid). Make sure they are not applications containing important data!
  2. Make sure you have Package-x-generic-16.pngabrt-cli installed: su -c 'yum install abrt-cli'

How to test

  1. Run abrt-cli list to show unreported crashes
  2. Run abrt-cli list --full to show all crashes
  3. Try crash reporting: run abrt-cli report DIR to report a crash to e.g. Logger
    • Select reporting using Logger
  4. Run abrt-cli rm DIR to delete the report

Expected Results

  1. Option list shows all not-yet-reported crashes
  2. Option list --full shows all crashes
  3. Option report shows crash report and asks for confirmation before sending it
    • ABRT asks you to choose one of the analyzer 'local GDB debugger' or 'retrace sever' and then analyzes the crash and creates a report. When the report is ready, abrt-cli opens a text editor with the content of the report. You can see what's being reported, and you are able to fill in instructions on how to reproduce the crash and other comments.
    • You are asked if you want to execute some reporter plugins or not.
  4. Option rm deletes crash
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_CLI&oldid=254450"