QA:Testcase ABRT CLI

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(proof)
Line 2: Line 2:
 
|description=This test case tests the functionality of the [[Features/ABRT|ABRT]] command line interface.  
 
|description=This test case tests the functionality of the [[Features/ABRT|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: <pre>kill -SIGSEGV (pid)</pre>
+
# 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)}}
# First investigate them via ''abrt-gui'' &mdash; which packages crashed, when, version, etc.
+
# Check the information on each crash from the graphical front end {{command|abrt-gui}}
# Check that /etc/abrt/plugins/Bugzilla.conf and ~/.abrt/Bugzilla.conf does not contain login and password. ~/.abrt/Bugzilla.conf might not even exist if you didn't create it.
+
# 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 <pre>abrt-cli --get-list-full</pre> in terminal to show all crashes.
+
# Run {{command|abrt-cli --get-list-full}} in terminal to show all crashes
# Run <pre>abrt-cli --get-list</pre> to show unreported crashes.
+
# Run {{command|abrt-cli --get-list}} to show unreported crashes
# Try crash reporting: run <pre>abrt-cli --report <uid>:<uuid></pre> to report a crash, identifying it via UID:UUID pair. UIDs and UUIDs can be found in --get-list[-full] output.
+
# 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 analyzes the crash and creates a report about it. This might take a while. When the report is ready, ''abrt-cli'' opens 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.
+
## 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 will be asked if you want to report using some reporter plugin. 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
## When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password.
+
## When reporting via Bugzilla plugin, ''abrt-cli'' should ask for login and password
# Create ~/.abrt/Bugzilla.conf:
+
# Create {{filename|~/.abrt/Bugzilla.conf}} with the contents:
#: <code>Login=your@email.org</code>
+
#:<pre>
#: <code>Password=yourpassword</code>
+
#:Login=your@email.org
# Try the crash reporting again, this time using <pre>abrt-cli --report @<x></pre> to report a crash using its ordinal number <x>. This time ''abrt-cli'' takes your login and password from the configuration file instead of asking you.
+
#:Password=yourpassword
# Another short form is <pre>abrt-cli --report <uuid_prefix></pre>Prefix must be unique, otherwise abrt-cli will complain.
+
#:</pre>
# Run <pre>abrt-cli --report-always <uuid-or-@x></pre> to report the crash without confirming, using all reporters associated with the crash.
+
# 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 <pre>abrt-cli --delete <uuid-or-@x></pre> to delete item with chosen UUID or ordinal number
+
# 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''' shows all crashes
+
# Option '''--get-list-full''' should show all crashes
# Option '''--get-list''' shows all not-yet-reported crashes
+
# Option '''--get-list''' should show all not-yet-reported crashes
# Option '''--report''' shows 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''' sends crash report
+
# Option '''--report-always''' should send crash report
# Option '''--delete''' deletes crash
+
# Option '''--delete''' should delete crash
 
}}
 
}}
 
[[Category:ABRT_Test_Cases]]
 
[[Category:ABRT_Test_Cases]]

Revision as of 05:41, 1 April 2010

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. Check the information on each crash from the graphical front end abrt-gui
  3. Check whether /etc/abrt/plugins/Bugzilla.conf and ~/.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
  4. Run abrt-cli --get-list-full in terminal to show all crashes
  5. Run abrt-cli --get-list to show unreported crashes
  6. Try crash reporting: run 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
    1. ABRT should analyze the crash and creates a report about it. This might take a while. 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. When you are done with the report, save your changes and close the editor
    2. 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
    3. When reporting via Bugzilla plugin, abrt-cli should ask for login and password
  7. Create ~/.abrt/Bugzilla.conf with the contents:
    Login=your@email.org
    Password=yourpassword
  8. Try the crash reporting again, this time using abrt-cli --report @(x) to report a crash using its ordinal number (x). This time abrt-cli should take your login and password from the configuration file instead of asking you
  9. Run abrt-cli --report-always (uuid-or-@x) to report a crash without confirming, using all reporters associated with the crash
  10. Run abrt-cli --delete (uuid-or-@x) to delete the report with the chosen UUID or ordinal number

Expected Results

  1. Option --get-list-full should show all crashes
  2. Option --get-list should show all not-yet-reported crashes
  3. Option --report should show crash report and asks for confirmation before sending it
  4. Option --report-always should send crash report
  5. Option --delete should delete crash