View Revisions: Issue #4242
Summary | 0004242: Testing of scripted module that depend on loadable module fails | ||
---|---|---|---|
Revision | 2018-05-30 12:28 by lassoan | ||
Steps To Reproduce | This fails (for example in https://app.assembla.com/spaces/slicerrt/subversion/source/HEAD/trunk/SlicerRt/src/DicomRtImportExport/Testing/Python/CMakeLists.txt): <pre> The problem seems to be that although the correct paths are stored in AdditionalLauncherSettings.ini in [LibraryPaths], they are not used as additional module paths. This workaround makes the test pass: <pre> WITH_GENERIC_TESTS) #----------------------------------------------------------------------------- Register the unittest subclass in the main script as a ctest.Note that the test will also be available at runtime.slicer_add_python_unittest( TODO: slicer_add_python_unittest should take care of adding the additional module pathsSLICER_ARGS |
||
Revision | 2016-08-04 18:52 by lassoan | ||
Steps To Reproduce | This fails (for example in https://app.assembla.com/spaces/slicerrt/subversion/source/HEAD/trunk/SlicerRt/src/DicomRtImportExport/Testing/Python/CMakeLists.txt): slicerMacroBuildScriptedModule( The problem seems to be that although the correct paths are stored in AdditionalLauncherSettings.ini in [LibraryPaths], they are not used as additional module paths. This workaround makes the test pass: #----------------------------------------------------------------------------- WITH_GENERIC_TESTS) #----------------------------------------------------------------------------- Register the unittest subclass in the main script as a ctest.Note that the test will also be available at runtime.slicer_add_python_unittest( TODO: slicer_add_python_unittest should take care of adding the additional module pathsSLICER_ARGS |