From Fedora Project Wiki
(convert to new category system) |
No edit summary |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case tests the functionality of the | |||
|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= | ||
# Run {{command|abrt-cli list}} to show unreported crashes | |||
# Run {{command|abrt-cli list --full}} to show all crashes | |||
# Try crash reporting: run {{command|abrt-cli report <tt>DIR</tt>}} to report a crash to e.g. Logger | |||
# Run {{command|abrt-cli | #* Select reporting using Logger | ||
# Run {{command|abrt-cli -- | # Run {{command|abrt-cli rm <tt>DIR</tt>}} to delete the report | ||
# Try crash reporting: run {{command|abrt-cli | |||
# | |||
# Run {{command|abrt-cli | |||
|results= | |results= | ||
# Option ''' | # Option '''list''' shows all not-yet-reported crashes | ||
# Option '''-- | # Option '''list --full''' shows all crashes | ||
# Option ''' | # 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, {{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 ''' | #* You are asked if you want to execute some reporter plugins or not. | ||
# Option '''rm''' deletes crash | |||
}} | }} | ||
[[Category:Package_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
- 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! - Make sure you have
abrt-cli
installed:su -c 'yum install abrt-cli'
How to test
- Run
abrt-cli list
to show unreported crashes - Run
abrt-cli list --full
to show all crashes - Try crash reporting: run
abrt-cli report DIR
to report a crash to e.g. Logger- Select reporting using Logger
- Run
abrt-cli rm DIR
to delete the report
Expected Results
- Option 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
- 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.
- 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,
- Option rm deletes crash