ITK/Release 4/Modularization/ Add tests: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
*Regression tests: need test driver
== Regression tests: need test driver ==


Approach a: stand-alone regression test
Approach a: stand-alone regression test


Approach b: using the test driver macro
Approach b: using the test driver macro
Line 9: Line 12:




*Non-regression tests
== Non-regression tests ==
add_executable( [executable name] [source file or files])
The same way it used to be, except the "add_test" command:
 
*add_executable( [executable name] [source file or files])


target_link_libraries([executable name] <name of libraries])
*target_link_libraries([executable name] <name of libraries])


add_test(NAME [test name]  COMMAND [executable name] [arguments])
*adopt the modern CMake syntax :[NAME, COMMAND]: add_test(NAME [test name]  COMMAND [executable name] [arguments])  


   e.g. add_executable(itkBinaryThresholdFilterTest itkBinaryThresholdFilterTest.cxx)
   e.g. add_executable(itkBinaryThresholdFilterTest itkBinaryThresholdFilterTest.cxx)

Revision as of 15:54, 4 April 2011

Regression tests: need test driver

Approach a: stand-alone regression test



Approach b: using the test driver macro



Non-regression tests

The same way it used to be, except the "add_test" command:

  • add_executable( [executable name] [source file or files])
  • target_link_libraries([executable name] <name of libraries])
  • adopt the modern CMake syntax :[NAME, COMMAND]: add_test(NAME [test name] COMMAND [executable name] [arguments])
 e.g. add_executable(itkBinaryThresholdFilterTest itkBinaryThresholdFilterTest.cxx)
      target_link_libraries(itkBindaryThresholdFilterTest ${ITK-BinaryThreshold_LIBRARIES})
      add_test(NAME itkBinaryThresholdFilterTest  
            COMMAND itkBinaryThresholdFilterTest input.png output.png)