We noticed that the PATH is different when executing tests directly by running a test driver compared to calling ctest. For all tests we set the PATH environment as test target property. The creation of this property is flawed as we override the PATH instead of appending to the PATH.
|Resolved||kislinsk||T26888 MITK_BUILD_CONFIGURATION "All" reveals some failing tests on CI build clients|
|Resolved||kislinsk||T26965 MitkREST module tests fail on Windows when executed via ctest but work when executed directly|