Improve docs formatting
This commit is contained in:
parent
b45006e9a3
commit
0a4200bbb3
|
@ -198,10 +198,10 @@ Using the builtin breakpoint function
|
||||||
Python 3.7 introduces a builtin ``breakpoint()`` function.
|
Python 3.7 introduces a builtin ``breakpoint()`` function.
|
||||||
Pytest supports the use of ``breakpoint()`` with the following behaviours:
|
Pytest supports the use of ``breakpoint()`` with the following behaviours:
|
||||||
|
|
||||||
- When breakpoint() is called and PYTHONBREAKPOINT is set to the default value, PyTest will use the Custom PDB trace UI instead of the system default Pdb.
|
- When ``breakpoint()`` is called and ``PYTHONBREAKPOINT`` is set to the default value, pytest will use the custom internal PDB trace UI instead of the system default ``Pdb``.
|
||||||
- When tests are complete, the system will default back to the system Pdb trace UI.
|
- When tests are complete, the system will default back to the system ``Pdb`` trace UI.
|
||||||
- If --pdb is called on execution of Pytest, the custom Pdb interface is used on bothbreakpoint() and failed tests/unhandled exceptions.
|
- If ``--pdb`` is called on execution of pytest, the custom internal Pdb trace UI is used on ``bothbreakpoint()`` and failed tests/unhandled exceptions.
|
||||||
- If --pdbcls is used, the custom class will be executed when a test fails (as expected within existing behaviour), but also when breakpoint() is called from within a test, the custom class debugger will be instantiated.
|
- If ``--pdbcls`` is used, the custom class debugger will be executed when a test fails (as expected within existing behaviour), but also when ``breakpoint()`` is called from within a test, the custom class debugger will be instantiated.
|
||||||
|
|
||||||
.. _durations:
|
.. _durations:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue