From Fedora Project Wiki

No edit summary
(minor cleanups)
Line 3: Line 3:
|description=This test case tests the functionality of the ABRT command line interface.  
|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=
# After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing with the command {{command|kill -SIGSEGV (pid)}}
# Make sure you have {{package||abrt-cli}} installed
# Run {{command|abrt-cli --list}} to show unreported crashes
# Run {{command|abrt-cli --list}} to show unreported crashes
# Run {{command|abrt-cli --list --full}} to show all crashes
# Run {{command|abrt-cli --list --full}} to show all crashes
# Try crash reporting: run {{command|abrt-cli --report <tt>CRASH_DIR</tt>}} to report a crash to e.g. Logger
# Try crash reporting: run {{command|abrt-cli --report <tt>CRASH_DIR</tt>}} to report a crash to e.g. Logger
# Run {{command|abrt-cli --delete <tt>CRASH_DIR</tt>}} to delete the report.
# Run {{command|abrt-cli --delete <tt>CRASH_DIR</tt>}} to delete the report
 
|results=
|results=
# Option '''--list --full''' should show all crashes
# Option '''--list --full''' should show all crashes
# Option '''--list''' should show all not-yet-reported crashes
# Option '''--list''' should show all not-yet-reported crashes
# Option '''--report''' should show crash report and asks for confirmation before sending it
# Option '''--report''' should show crash report and asks for confirmation before sending it
#* ABRT should analyze the crash and create a report about it. When the report is ready, {{command|abrt-cli}} should open a text editor with the content of the report. You can see what is being reported, and you can fill in instructions on how to reproduce the crash and other comments. Close the editor.
#* ABRT should analyze the crash and create a report about it. When the report is ready, {{command|abrt-cli}} should open a text editor with the content of the report. You can see what is being reported, and you can fill in instructions on how to reproduce the crash and other comments. Close the editor
#* You should be asked if you want to report using some reporter plugins. Respond ''Y'' for Bugzilla reporter, and ''N'' to skip reporting using Logger.
#* You should be asked if you want to report using some reporter plugins. Respond ''Y'' for Bugzilla reporter, and ''N'' to skip reporting using Logger
# Option '''--delete''' should delete crash
# Option '''--delete''' should delete crash
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 18:28, 29 March 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 CRASH_DIR to report a crash to e.g. Logger
  4. Run abrt-cli --delete CRASH_DIR to delete the report

Expected Results

  1. Option --list --full should show all crashes
  2. Option --list should show all not-yet-reported crashes
  3. Option --report should show crash report and asks for confirmation before sending it
    • ABRT should analyze the crash and create a report about it. When the report is ready, abrt-cli should open a text editor with the content of the report. You can see what is being reported, and you can fill in instructions on how to reproduce the crash and other comments. Close the editor
    • You should be asked if you want to report using some reporter plugins. Respond Y for Bugzilla reporter, and N to skip reporting using Logger
  4. Option --delete should delete crash
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_CLI&oldid=229642"