https://www.slicer.org/w/index.php?action=history&feed=atom&title=Documentation%2F4.10%2FDevelopers%2FFAQ%2FTesting 2026-05-06T21:04:34Z Revision history for this page on the wiki MediaWiki 1.33.0 https://www.slicer.org/w/index.php?title=Documentation/4.10/Developers/FAQ/Testing&diff=59735&oldid=prev 2018-10-19T00:41:37Z

<p>Nightly -&gt; 4.10</p> <p><b>New page</b></p><div>&lt;noinclude&gt;{{documentation/versioncheck}}&lt;/noinclude&gt;<br /> &lt;noinclude&gt;__TOC__<br /> ={{#titleparts: {{PAGENAME}} | | -1 }}=&lt;/noinclude&gt;&lt;includeonly&gt;<br /> ='''Developer FAQ: {{{1}}}'''=<br /> &lt;/includeonly&gt;<br /> <br /> <br /> == What is the difference between add_test, simple_test, slicer_add_python_test, and slicer_add_python_unittest CMake macros/functions ? ==<br /> <br /> * [https://cmake.org/cmake/help/latest/command/add_test.html add_test]: provided by CMake and allows to add a test that can be executed using [https://cmake.org/cmake/help/latest/manual/ctest.1.html ctest].<br /> <br /> * &lt;code&gt;simple_test(testname)&lt;/code&gt;:<br /> ** Usually called after configuring a test driver using &lt;code&gt;SlicerMacroConfigureModuleCxxTestDriver&lt;/code&gt;. <br /> ** Accept the same arguments as &lt;code&gt;add_test&lt;/code&gt;.<br /> ** Conveniently call [https://cmake.org/cmake/help/latest/module/ExternalData.html#command:externaldata_add_test ExternalData_add_test] with the appropriate parameters.<br /> ** Set the &lt;code&gt;LABELS&lt;/code&gt; test property.<br /> ** Invoke test driver using &lt;code&gt;${Slicer_LAUNCH_COMMAND}&lt;/code&gt;<br /> &lt;!--<br /> ** It internally check if a variable &lt;code&gt;KIT&lt;/code&gt; is set in the current scope, if not set it first defaults to the value of value of &lt;code&gt;CLP&lt;/code&gt; variable automatically set after building a CLI using &lt;code&gt;SEMMacroBuildCLI&lt;/code&gt;. If not building a CLI, it then defaults to the value of &lt;code&gt;EXTENSION_NAME&lt;/code&gt; variable.<br /> ** Ideally, this macro should be renamed to &lt;code&gt;slicer_add_test&lt;/code&gt;<br /> --&gt;<br /> <br /> * &lt;code&gt;slicer_add_python_unittest(SCRIPT script [TESTNAME_PREFIX prefix] [SLICER_ARGS slicer_arg1 [slicer_arg2 [...]]])&lt;/code&gt;:<br /> ** Run unittests with Slicer using &lt;code&gt;--python-code &quot;import slicer.testing\\; slicer.testing.runUnitTest(['${CMAKE_CURRENT_BINARY_DIR}', '${_script_source_dir}'], '${test_name}')&quot;&lt;/code&gt;.<br /> ** Slicer arguments systematically passed are &lt;code&gt;--testing&lt;/code&gt; and &lt;code&gt;--no-splash&lt;/code&gt;.<br /> ** Conveniently call [https://cmake.org/cmake/help/latest/module/ExternalData.html#command:externaldata_add_test ExternalData_add_test] with the appropriate parameters.<br /> <br /> * &lt;code&gt;slicer_add_python_test(SCRIPT script [TESTNAME_PREFIX prefix] [SLICER_ARGS slicer_arg1 [slicer_arg2 [...]]] [SCRIPT_ARGS script_arg1 [script_arg2 [..]]])&lt;/code&gt;:<br /> ** Useful to run a python test that can not be added as a unittest.<br /> ** Run Slicer with the given &lt;code&gt;script&lt;/code&gt;.<br /> ** Slicer arguments systematically passed are &lt;code&gt;--testing&lt;/code&gt; and &lt;code&gt;--no-splash&lt;/code&gt;.<br /> ** Conveniently call [https://cmake.org/cmake/help/latest/module/ExternalData.html#command:externaldata_add_test ExternalData_add_test] with the appropriate parameters.<br /> <br /> == What is the meaning of prefix py_ in test name ? ==<br /> <br /> It means that the test is implemented in python.</div>

UpdateBot