Capitalize headlines (#8008)
This commit is contained in:
parent
c784c142a4
commit
9bc633064b
|
@ -544,7 +544,7 @@ Let's run this without capturing output and see what we get:
|
|||
.
|
||||
1 passed in 0.12s
|
||||
|
||||
marking platform specific tests with pytest
|
||||
Marking platform specific tests with pytest
|
||||
--------------------------------------------------------------
|
||||
|
||||
.. regendoc:wipe
|
||||
|
|
|
@ -452,7 +452,7 @@ and nothing when run plainly:
|
|||
|
||||
========================== no tests ran in 0.12s ===========================
|
||||
|
||||
profiling test duration
|
||||
Profiling test duration
|
||||
--------------------------
|
||||
|
||||
.. regendoc:wipe
|
||||
|
@ -498,7 +498,7 @@ Now we can profile which test functions execute the slowest:
|
|||
0.10s call test_some_are_slow.py::test_funcfast
|
||||
============================ 3 passed in 0.12s =============================
|
||||
|
||||
incremental testing - test steps
|
||||
Incremental testing - test steps
|
||||
---------------------------------------------------
|
||||
|
||||
.. regendoc:wipe
|
||||
|
@ -739,7 +739,7 @@ it (unless you use "autouse" fixture which are always executed ahead of the firs
|
|||
executing).
|
||||
|
||||
|
||||
post-process test reports / failures
|
||||
Post-process test reports / failures
|
||||
---------------------------------------
|
||||
|
||||
If you want to postprocess test reports and need access to the executing
|
||||
|
|
Loading…
Reference in New Issue