doc: document dune runtest for test stanza and inline tests

Signed-off-by: Ali Caglayan <[email protected]>

Author: Alizter

doc/reference/dune/test.rst

@@ -30,6 +30,10 @@ This defines an executable named ``mytest.exe``. These tests can be run by
 building the aliases ``runtest-mytest`` and ``runtest-expect_test``
 respectively. They will also be added to the ``runtest`` alias.
 
+You may also run the test directly by using ``dune runtest`` and passing the
+name of the test: ``dune runtest mytest``. If the test stanza was in a
+directory ``src/`` then it would be ``dune runtest src/mytest``. 
+
 If the directory also contains an ``expect_test.expected`` file, then
 ``expect_test`` will be used to define an expect test. That is, the test will be
 executed and its output will be compared to ``expect_test.expected``.

doc/tests.rst

@@ -42,35 +42,33 @@ call ``dune runtest`` from the shell (or the command alias ``dune test``). This
 will run all the tests defined in the current directory and any subdirectory
 recursively.
 
-Note that in any case, ``dune runtest`` is simply shorthand for building the
-``runtest`` alias, so you can always ask Dune to run the tests in conjunction
-with other targets by passing ``@runtest`` to ``dune build``. For instance:
-
-.. code:: console
-
-   $ dune build @install @runtest
-   $ dune build @install @test/runtest
-
-
 Running a Single Test
 ---------------------
 
-If you would only like to run a single test for your project, you may use ``dune
-exec`` to run the test executable (for the sake of this example,
-``project/tests/myTest.ml``):
+If you would only like to run a single test for your project, you may use
+``dune runtest`` to run the :doc:`test<reference/dune/test>` executable (for
+the sake of this example, ``project/tests/myTest.ml``):
 
 .. code:: console
 
-  $ dune exec project/tests/myTest.exe
+  $ dune runtest project/tests/myTest
 
-To run :ref:`cram-tests` you can pass their paths to the ``dune test``  command.
+To run :ref:`cram-tests` you can pass their paths to the ``dune runtest``
+command.
 
 .. code:: console
 
-   $ dune test tests/myCramTest.t
+   $ dune runtest tests/myCramTest.t
 
 This works both for directory and file cram tests.
 
+Library stanzas with :ref:`inline tests<inline_tests>` enabled may also be run
+by passing the name of the library:
+
+.. code:: console
+
+   $ dune runtest tests/myinlinetestlib
+
 Running Tests in a Directory
 ----------------------------
 
@@ -461,6 +459,8 @@ this is only an example. We don't recommend using ``sed`` in your
 build, as this would cause portability problems.
 
 
+.. _test_stanza:
+
 Custom Tests
 ============