From Fedora Project Wiki

(convert to new category system)
(ABRT 2 updates)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] command line interface.  
 
|description=This test case tests the functionality of the ABRT command line interface.  
 
|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)}}
# Check the information on each crash from the graphical front end {{command|abrt-gui}}
# Run {{command|abrt-cli --list}} to show unreported crashes
# Check whether {{filename|/etc/abrt/plugins/Bugzilla.conf}} and {{filename|~/.abrt/Bugzilla.conf}} contain your Bugzilla login and password. The second file may not exist, which is fine. If these files do contain the information, remove it
# Run {{command|abrt-cli --list --full}} to show all crashes
# Run {{command|abrt-cli --get-list-full}} in terminal to show all crashes
# Try crash reporting: run {{command|abrt-cli --report <tt>CRASH_DIR</tt>}} to report a crash to e.g. Logger
# Run {{command|abrt-cli --get-list}} to show unreported crashes
# Run {{command|abrt-cli --delete <tt>CRASH_DIR</tt>}} to delete the report.
# Try crash reporting: run {{command|abrt-cli --report (uid):(uuid)}} to report a crash, identifying it via UID:UUID pair. UIDs and UUIDs can be found in --get-list[-full] output
 
## ABRT should analyze the crash and creates a report about it. This might take a while. 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. When you are done with the report, save your changes and 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
## When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password
# Create {{filename|~/.abrt/Bugzilla.conf}} with the contents:
#:<pre>
#:Login=your@email.org
#:Password=yourpassword
#:</pre>
# Try the crash reporting again, this time using {{command|abrt-cli --report @(x)}} to report a crash using its ordinal number (x). This time {{command|abrt-cli}} should take your login and password from the configuration file instead of asking you
# Run {{command|abrt-cli --report-always (uuid-or-@x)}} to report a crash without confirming, using all reporters associated with the crash
# Run {{command|abrt-cli --delete (uuid-or-@x)}} to delete the report with the chosen UUID or ordinal number
|results=
|results=
# Option '''--get-list-full''' should show all crashes
# Option '''--list --full''' should show all crashes
# Option '''--get-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
# Option '''--report-always''' should send crash report
#* 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.
# Option '''--delete''' should delete crash
# Option '''--delete''' should delete crash
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 18:16, 15 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. Run abrt-cli --list to show unreported crashes
  3. Run abrt-cli --list --full to show all crashes
  4. Try crash reporting: run abrt-cli --report CRASH_DIR to report a crash to e.g. Logger
  5. 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=227092"