I think what you are looking for is nose. It works like a test runner for unittest.
You can drop into the debugger on errors, with the following command:
nosetests --pdb
More Related Contents:
- How do I run all Python unit tests in a directory?
- Running a single test from unittest.TestCase via the command line
- Python Mocking a function from an imported module
- How to test Python 3.4 asyncio code?
- Python: Write unittest for console print
- What is the difference between setUp() and setUpClass() in Python unittest?
- Why doesn’t Python run my bash code?
- PATH issue with pytest ‘ImportError: No module named YadaYadaYada’
- Running unittest with typical test directory structure
- Run / Debug a Django application’s UnitTests from the mouse right click context menu in PyCharm Community Edition?
- Can I patch a Python decorator before it wraps a function?
- Python unit test with base and sub class
- Python unittest passing arguments
- Getting Python’s unittest results in a tearDown() method
- Why python mock patch doesn’t work?
- Python Mock object with method called multiple times
- How can I write unit tests against code that uses matplotlib?
- How can I create a ramdisk in Python?
- cannot override sys.excepthook
- How can I disable logging while running unit tests in Python Django?
- Attaching a process with pdb
- Can Python’s unittest test in parallel, like nose can?
- Step-by-step debugging with IPython
- Python mock Patch os.environ and return value
- Customizing unittest.mock.mock_open for iteration
- Is it possible for a unit test to assert that a method calls sys.exit()?
- pydev breakpoints not working
- How to watch for a variable change in python without dunder setattr or pdb
- Can I “fake” a package (or at least a module) in python for testing purposes?
- How to mock a readonly property with mock?