diff --git a/docs/_static/img/reframe-test-cases.svg b/docs/_static/img/reframe-test-cases.svg
index 511a51fe81..6af6e8c9bc 100644
--- a/docs/_static/img/reframe-test-cases.svg
+++ b/docs/_static/img/reframe-test-cases.svg
@@ -1,3 +1,3 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/docs/pipeline.rst b/docs/pipeline.rst
index 7f3172565d..3d9438fa6a 100644
--- a/docs/pipeline.rst
+++ b/docs/pipeline.rst
@@ -3,7 +3,7 @@ How ReFrame Executes Tests
==========================
A ReFrame test will be normally tried for different programming environments and different partitions within the same ReFrame run.
-These are defined in the test's :func:`__init__` method, but it is not this original test object that is scheduled for execution.
+These can be defined in the test's class body, in a post-init hook or in its :func:`__init__` method, but it is not this original test object that is scheduled for execution.
The following figure explains in more detail the process:
.. figure:: _static/img/reframe-test-cases.svg