summaryrefslogtreecommitdiff
path: root/doc/en/example
diff options
context:
space:
mode:
authorfrankgerhardt <frank.gerhardt@gmail.com>2020-11-08 02:44:04 +0100
committerGitHub <noreply@github.com>2020-11-07 22:44:04 -0300
commit9bc633064b141894d74220cca537b0646182a176 (patch)
tree36e67b751e28781638fee0ba257e5bcdaa21c20a /doc/en/example
parentc784c142a4a68296748353fb017aa6c13582dbb8 (diff)
downloadpytest-9bc633064b141894d74220cca537b0646182a176.tar.gz
Capitalize headlines (#8008)
Diffstat (limited to 'doc/en/example')
-rw-r--r--doc/en/example/markers.rst2
-rw-r--r--doc/en/example/simple.rst6
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/en/example/markers.rst b/doc/en/example/markers.rst
index 1dc44be34..f0effa026 100644
--- a/doc/en/example/markers.rst
+++ b/doc/en/example/markers.rst
@@ -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
diff --git a/doc/en/example/simple.rst b/doc/en/example/simple.rst
index e9952dad4..b641e61f7 100644
--- a/doc/en/example/simple.rst
+++ b/doc/en/example/simple.rst
@@ -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