Formulation details in the documentation.

Author: RKrahl

doc/src/advanced.rst

@@ -17,11 +17,12 @@ Consider the following example test module:
 .. literalinclude:: ../examples/dyn-parametrized.py
 
 In principle, this example works the very same way as the basic
-example for parametrized tests, see :ref:`usage-parametrized`.  The
-only difference is that the lists of paramters are dynamically
-compiled beforehand.  The test for child `l` deliberately fails, just
-to show the effect.  As a consequence, the test for its parent `d`
-will be skipped.
+example for :ref:`usage-parametrized`.  The only difference is that
+the lists of paramters are dynamically compiled beforehand.  The test
+for child `l` deliberately fails, just to show the effect.  As a
+consequence, the test for its parent `d` will be skipped.
+
+.. _advanced-grouping-fixtures:
 
 Grouping tests using fixtures
 -----------------------------

doc/src/usage.rst

@@ -44,10 +44,10 @@ Naming tests
 Tests are referenced by their name in the `depends` argument.  The
 default for this name is the node ID defined by pytest, that is the
 name of the test function, extended by the parameters if applicable.
-As these node IDs may become complicated, the name can be overridden
-by an explicit `name` argument to the marker.  The following example
-works exactly as the last one, only the test names are explicitely
-set:
+In some cases, it's not easy to predict the names of the node IDs.
+For this reason, the name of the tests can be overridden by an
+explicit `name` argument to the marker.  The following example works
+exactly as the last one, only the test names are explicitely set:
 
 .. literalinclude:: ../examples/named.py
 
@@ -100,3 +100,9 @@ Tests `test_c` and `test_d` set their dependencies at runtime calling
 of the `request` pytest fixture, the second argument is the list of
 dependencies.  It has the same effect as passing this list as the
 `depends` argument to the :func:`pytest.mark.dependency` marker.
+
+The present example is certainly somewhat artificial, as the use of
+the :func:`pytest_dependency.depends` function would not be needed in
+such a simple case.  For a more involved example that can not as
+easily be formulated with the static the `depends` argument, see
+:ref:`advanced-grouping-fixtures`.