Skip to content
Open
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions docs/guides/contributing/unit_tests.rst
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,27 @@ For verbose test output (listing each test and result status), run::

ctest -V

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word "should" appears twice on line 22, please correct that too.

You can also run single test categories or individual tests. To view a list of
availble tests, run::

ctest -N

You can run specific groups of tests by name using the ``-R`` (match by regex)
option, for example::

ctest -V -R test_cpu
ctest -V -R test_gpu
ctest -V -R test_python

You can also run individual test directly using ``--run_only``, for example to
run only the CPU unit tests from the Builtins suite::

tests/cpu/test_cpu_exec --run_only Builtins

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add the following:

Additional options for the CPU tests, such as --stop_on_error are described using the --help option:

tests/cpu/test_cpu_exec --help

Similarly you can run just Python tests directly::

python3 tests/python/OpenColorIOTestSuite.py
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove lines 47-50, it is better to just run those via ctest as described on line 40.


Test framework
==============

Expand Down