DOC Added additional tips for pytest usage (#13540)

* Added additional tips for pytest

* Added --ff option

* typo

doc/developers/contributing.rst

@@ -643,6 +643,8 @@ We expect code coverage of new features to be at least around 90%.
 
    3. Loop.
 
+For guidelines on how to use ``pytest`` efficiently, see the
+:ref:`pytest_tips`.
 
 
 Developers web site

doc/developers/tips.rst

@@ -61,6 +61,9 @@ integration, consider `this browser extension
 <https://github.com/codecov/browser-extension>`_. The coverage of each line
 will be displayed as a color background behind the line number.
 
+
+.. _pytest_tips:
+
 Useful pytest aliases and flags
 -------------------------------
 
@@ -90,6 +93,20 @@ When a unit test fails, the following tricks can make debugging easier:
 
          pytest --pdbcls=IPython.terminal.debugger:TerminalPdb --capture no
 
+Other `pytest` options that may become useful include:
+
+  - ``-x`` which exits on the first failed test
+  - ``--lf`` to rerun the tests that failed on the previous run
+  - ``--ff`` to rerun all previous tests, running the ones that failed first
+  - ``-s`` so that pytest does not capture the output of ``print()``
+    statements
+  - ``--tb=short`` or ``--tb=line`` to control the length of the logs
+
+Since our continuous integration tests will error if ``DeprecationWarning``
+or ``FutureWarning`` aren't properly caught, it is also recommended to run
+``pytest`` along with the ``-Werror::DeprecationWarning`` and
+``-Werror::FutureWarning`` flags.
+
 .. _saved_replies:
 
 Standard replies for reviewing