p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix syntax

This commit is contained in:
Anthony Shaw 2018-03-27 21:26:55 +11:00
parent 671ab5a36c
commit b45006e9a3
No known key found for this signature in database
GPG Key ID: AB4A19AE1CE85744
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/en/usage.rst
View File

@ -190,7 +190,7 @@ in your code and pytest automatically disables its output capture for that test:
and continue with the regular test run. and continue with the regular test run.
.. _breakpoint-builtin: .. _`breakpoint-builtin`:
Using the builtin breakpoint function Using the builtin breakpoint function
------------------------------------- -------------------------------------
@ -200,8 +200,7 @@ 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 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 both - If --pdb is called on execution of Pytest, the custom Pdb interface is used on bothbreakpoint() and failed tests/unhandled exceptions.
breakpoint() 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 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: