Search results

From KitwarePublic
Jump to navigationJump to search
  • ...places a burden on the cdash database. Furthermore, some hypothesize that test output size may affect the performance of cdash. ...oks at the size of output produced by ITKv4 and looks for ways to reduce a test's output.
    6 KB (819 words) - 22:19, 4 October 2011
  • * Dashboard failing test ** chiarugi Iowa and Tcl test seg faulting (64bit).
    973 bytes (122 words) - 15:17, 20 April 2007
  • ...llows us to test functionality in CDash (such as javascript) that we can't test with PHP alone. ...eb browser as you normally would to record the behavior that you'd like to test.
    2 KB (399 words) - 15:44, 10 November 2013
  • ...ality, please read [[CDash:Build Management]]. This page describes how to test this functionality in CDash. The build management test in CDash is split into three parts. First, the client registers with CDash
    5 KB (751 words) - 18:03, 28 June 2010
  • * ResampleImageFilter new ReferenceImage had no test. ** How to prevent developers from adding new features without a test ?
    1,002 bytes (110 words) - 19:49, 5 April 2007
  • *** Add test for resampling image of std::complex * Add test for resampling image of std::complex
    806 bytes (120 words) - 18:54, 4 December 2009
  • = How to Add a Test in ITK = * Write the test itself
    8 KB (1,344 words) - 04:52, 4 February 2011
  • * New Wiki page describing how to add a Test to ITK
    260 bytes (39 words) - 16:15, 29 February 2008
  • * ResampleImageFilter new ReferenceImage had no test. ** How to prevent developers from adding new features without a test ?
    1 KB (120 words) - 15:02, 29 March 2007
  • # Try to find the full path to the test executable "--test-mode --script ${slicerScriptFile}"
    5 KB (665 words) - 23:12, 2 January 2009
  • * Reducing test time
    407 bytes (40 words) - 18:46, 26 July 2013
  • = How to Add a Test to ITK= * Write the test
    9 KB (1,384 words) - 18:47, 28 January 2019
  • === Following is the test to see if source code insertion works ===
    1 KB (200 words) - 21:32, 3 January 2011
  • Using the test driver macro All the tests in one module share one test driver.
    6 KB (771 words) - 15:01, 16 April 2016
  • * Before removing we should identify test that will be good for benchmarking before/after * Luis identify ITK test with realistic cases for Julie and Julien.
    1 KB (158 words) - 16:01, 9 December 2011
  • ...amic Analysis:''' reports the memory allocation/deallocations analysis for test, examples and executable for the project. Valgrind is currently supported *** '''Tests:''' Overview of the test failing for this day and this project
    22 KB (3,462 words) - 17:50, 27 October 2016
  • = Benchmark Test = Quick Test that verify correctness are available here:
    4 KB (657 words) - 16:01, 9 December 2011
  • The ITK method for handling test data is the [[ITK/Git/Develop/Data#ExternalData | CMake/ExternalData]] meth # Add testing data references in you ''test/CMakeLists.txt'' as you normally would, i.e. use '''itk_add_test''' and wit
    3 KB (423 words) - 17:07, 17 September 2013
  • and a test is available at ./test/itkLBFGSBOptimizerTest.cxx
    1 KB (171 words) - 16:01, 9 December 2011
  • * Create a minimalistic test that illustrates the incorrect behavior
    312 bytes (40 words) - 19:11, 30 January 2009

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)