Commit 3dfa0542 authored by Jean-Loup Haberbusch's avatar Jean-Loup Haberbusch
Browse files

UPDATED Testing

parent 6f8a0447
Pipeline #16738 passed with stages
in 26 seconds
......@@ -26,7 +26,7 @@ In the next section, this document present a (very limited and simple) explanati
Next, it shows how testing is done in the CamiTK framework and describe the automatic test framework provided by CamiTK (and what are the plans to improve it).
Finally, the last section explains the basic of adding new tests In CamiTK.
Please refer to [the CamiTK automatic tests framework](../dev/Automatic-Tests.md) for a practical guide on how to automatically generate tests for your extensions.
Please refer to [the CamiTK automatic tests framework](https://camitk.gricad-pages.univ-grenoble-alpes.fr/Docs/Highlighted%20Features/Automatic-Tests/) for a practical guide on how to automatically generate tests for your extensions.
## Cross-platform testing C++ code using CMake
......@@ -70,7 +70,7 @@ Another step is to check the test coverage, i.e., how much of the actual code li
CamiTK comes with a specific testing framework built on top of the CMake/CTest framework. This section describes the main level of tests that are used In the CamiTK Community Edition project.
!!! Note
the [automatic test](../dev/Automatic-Tests.md) defined for the CamiTK Community Edition can Be used In any other CEP independently. |
the [automatic test](https://camitk.gricad-pages.univ-grenoble-alpes.fr/Docs/Highlighted%20Features/Automatic-Tests/) defined for the CamiTK Community Edition can Be used In any other CEP independently.
### Unit testing
......@@ -101,7 +101,7 @@ This can also be used to profile the pipeline in terms of execution time or memo
All the test are ran each time a modification is detected on the git source code management system (on any branch). All tests are reported on the [CamiTK dashboard](https://cdash-timc.imag.fr/index.php).
Not only the test results are visible, but CamiTK also offers a way to check the [test code coverage](#camitk-community-edition-code-coverage) for the Community Edition or [an individual extension project](/Docs/dev/Automatic-Tests/#step-6-check-test-coverage-of-your-cep)
Not only the test results are visible, but CamiTK also offers a way to check the [test code coverage](#camitk-community-edition-code-coverage) for the Community Edition or [an individual extension project](https://camitk.gricad-pages.univ-grenoble-alpes.fr/Docs/Highlighted%20Features/Automatic-Tests/#step-6-check-test-coverage-of-your-cep)
## CamiTK testing framework
......@@ -115,7 +115,7 @@ The CamiTK testing framework is defined As a layer on top of CMake/CTest, and pr
The following sections describes these five different types of tests.
!!! Note
Automatic test for action and component extensions and pipeline of actions as well as test coverage procedures can be also used in any CamiTK Extension Project. Please check [the CamiTK developer guide](../dev/Automatic-Tests.md) for more information about how to use the CamiTK testing framework for your CEP.
Automatic test for action and component extensions and pipeline of actions as well as test coverage procedures can be also used in any CamiTK Extension Project. Please check [the CamiTK developer guide](https://camitk.gricad-pages.univ-grenoble-alpes.fr/Docs/Highlighted%20Features/Automatic-Tests/) for more information about how to use the CamiTK testing framework for your CEP.
### Automatic test of action and component extensions
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment