In order to maintain the test harness infrastructure, the test harness infrastructure was copied into Slicer treee (a single file: Modules/CLI/itkTestMain.h

This has been working for ITKv4 since 2011-04-04.

There is no compelling reason to conflate the move to ITKv4 with a change in the test harness. The test pass with the existing system.

===================

The itkTestMain.h was an internal test harness paradigm that was not intended as part of the exposed ITK API (it was the internal test harness mechanism used for ITK).

Other tools that may have re-used this internal mechansims will need to copy the from ITKv3 the support files for their test harness infrastructure.

Using the old test harness noes not change the behavior or utility of ITKv4.

=====
If one wishes to update their test harness (for whatever reason that would be) they should consider cmake native test harnesses, or google test harness, or other such infrastructures.

Since module are expected to be successfully build against both Slicer or SlicerExecutionModel only, this should then probably be moved into the SlicerExecutionModel.

JC,

Something like the following would be what I recommend for SEM:

###############################################################################
###############################################################################

MakeTestDriverFromSEMTool

For tools made with the slicer execution model,

This macro will build a test driver that adds the

--compare

--compareIntensityTolerance

--compareRadiusTolerance

--compareNumberOfPixelsTolerance

to the SEM tools.

macro(MakeTestDriverFromSEMTool SEMToolName SEMToolTestSourceName)
set(SEMToolLibName ${SEMToolName}Lib)

if(ITK_VERSION_MAJOR LESS 4)

BackPort files from ITKv4 need to be pushed to ITKv3 for backwards compatibility

include_directories(${BRAINSTools_SOURCE_DIR}/BRAINSCommonLib/itkV3TestKernel/include)

endif()

set(CMAKE_TESTDRIVER_BEFORE_TESTMAIN "#include \"itkTestDriverBeforeTest.inc\"")
set(CMAKE_TESTDRIVER_AFTER_TESTMAIN "#include \"itkTestDriverAfterTest.inc\"")

create_test_sourcelist(${SEMToolName} ${SEMToolName}TestDriver.cxx ${SEMToolTestSourceName}
EXTRA_INCLUDE itkTestDriverIncludeRequiredIOFactories.h
FUNCTION ProcessArgumentsAndRegisterRequiredFactories
)
add_executable(${SEMToolName}TestDriver ${SEMToolName}TestDriver.cxx ${SEMToolTestSourceName})
target_link_libraries(${SEMToolName}TestDriver ${SEMToolLibName} ${ITKTestKernel_LIBRARIES})
set_target_properties(${SEMToolName}TestDriver PROPERTIES
RUNTIME_OUTPUT_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}"
LIBRARY_OUTPUT_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}"
ARCHIVE_OUTPUT_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}"
)
endmacro()

=================================================

Where test driver is something like:

//
//A test driver to append the
//itk image processing test
//commands to an
//the SEM compatibile program
//

#ifdef WIN32
#define MODULE_IMPORT __declspec(dllimport)
#else
#define MODULE_IMPORT
#endif

extern "C" MODULE_IMPORT int ModuleEntryPoint(int, char* []);

int BRAINSFitTest(int argc, char* argv[])
{
return ModuleEntryPoint(argc, argv);
}

Thanks for the feedback. This is something we will be addressing during the hackfest.

If there are modules that need this done, then we coud work through that effort. I will take care of all the internal Slicer mechanisms once we no longer need to support ITKv3. Until then the task is too daunting to maintain both test harnesses.

any update?

All modules in Slicer compile against ITKv4 and this has been addressed during the Utah meeting.

Fixed in r21604
See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21604

Closing resolved issues that have not been updated in more than 3 months