From Fedora Project Wiki

(ABRT 2 updates)
No edit summary
Line 5: Line 5:
|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)}}
# 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

Revision as of 13:51, 17 March 2011

Description

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


How to test

  1. After running previous ABRT test cases you probably have a bunch of crash reports in cache. If not do some crashing with the command kill -SIGSEGV (pid)
  2. Make sure you have abrt-cli installed
  3. Run abrt-cli --list to show unreported crashes
  4. Run abrt-cli --list --full to show all crashes
  5. Try crash reporting: run abrt-cli --report CRASH_DIR to report a crash to e.g. Logger
  6. 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