From Fedora Project Wiki
No edit summary |
(updated to match current abrt) |
||
Line 13: | Line 13: | ||
#: File "/usr/bin/pydoc", line 3, in <module> | #: File "/usr/bin/pydoc", line 3, in <module> | ||
#: 0/0 | #: 0/0 | ||
# ABRT should catch the traceback, and if you inspect the report via {{command|abrt | # ABRT should catch the traceback, and if you inspect the report via {{command|gnome-abrt}}, the trace in report window should be the same as in the terminal where you executed the command | ||
# The ABRT plugin should not cause any unintended behaviour in python scripts when installed | # The ABRT plugin should not cause any unintended behaviour in python scripts when installed | ||
}} | }} | ||
[[Category:Package_abrt_test_cases]] | [[Category:Package_abrt_test_cases]] |
Revision as of 12:22, 3 May 2013
Description
This test case tests the functionality of the ABRT Python exception handler.
How to test
- Ensure the package is installed:
su -c 'yum install abrt-addon-python'
- Find a python
.py
file which is part of an official Fedora package. For example,/usr/bin/pydoc
which is provided by thepython
package. Other files you might use for experiments: /usr/bin/pygtk-demo, /usr/bin/yum, /usr/bin/fetch_file - Make a back-up of the file:
su -c 'cp -a /usr/bin/pydoc /usr/bin/pydoc.save'
- Edit the file to contain some invalid Python code. Add "0/0" (without quotes) line near the top (after the line which begins with #).
- Execute the modified file.
- Revert the modified python file:
su -c 'cp -a /usr/bin/pydoc.save /usr/bin/pydoc'
Expected Results
- A python traceback should be generated at the command line:
- Traceback (most recent call last):
- File "/usr/bin/pydoc", line 3, in <module>
- 0/0
- ABRT should catch the traceback, and if you inspect the report via
gnome-abrt
, the trace in report window should be the same as in the terminal where you executed the command - The ABRT plugin should not cause any unintended behaviour in python scripts when installed