Search results

From KitwarePublic
Jump to navigationJump to search

Page title matches

Page text matches

  • project(Test) add_executable(Test Test.cxx)
    1 KB (173 words) - 17:53, 14 August 2012
  • ...akeLists.txt file, move most of the parameters to be hard-coded inside the test files. = Test Model =
    518 bytes (74 words) - 13:21, 11 July 2010
  • itk_module_test() # this macro takes care of the test module(ITKFooTest)'s dependencies itkFooHeaderTest.cxx # each module has a header test
    564 bytes (57 words) - 16:00, 9 December 2011
  • ADD_EXECUTABLE(Test test.cxx) TARGET_LINK_LIBRARIES (Test ITKBasicFilters ITKCommon ITKIO
    461 bytes (64 words) - 16:14, 20 March 2006
  • ADD_EXECUTABLE(Test KWHelloWorldExample-alex.cxx) TARGET_LINK_LIBRARIES (Test ITKBasicFilters ITKCommon ITKIO KWWidgets
    531 bytes (64 words) - 16:13, 20 March 2006
  • #REDIRECT [[Rating test]]
    25 bytes (3 words) - 21:11, 10 September 2009
  • This is a test.
    15 bytes (4 words) - 16:39, 17 August 2010
  • {{VTKCMakeLists|Test|Library1 Library2}}
    40 bytes (4 words) - 13:04, 4 November 2010
  • *** [http://code.google.com/p/googletest/wiki/GoogleTestPrimer Google Test Primer] *** Test "A" should return a value of 5, verify the test produces the correct value
    2 KB (251 words) - 18:20, 6 July 2010
  • This is a test page for mwdoc.
    30 bytes (7 words) - 17:51, 13 February 2013
  • = How to add a new TubeTK test = #Add baseline dataset for the new test ( if your test is a regression testing )
    3 KB (448 words) - 18:39, 26 July 2013
  • == Outstanding Test Failures == ** http://www.cdash.org/CDash/testDetails.php?test=134368000&build=1987166
    2 KB (186 words) - 12:46, 21 March 2012
  • === Following is the test to see if source code insertion works ===
    962 bytes (99 words) - 20:05, 28 February 2011
  • == Outstanding Test Failures == ** http://www.cdash.org/CDash/testDetails.php?test=134368000&build=1987166
    2 KB (205 words) - 13:33, 7 March 2012
  • == Outstanding Test Failures == ** http://www.cdash.org/CDash/testDetails.php?test=134368000&build=1987166
    2 KB (207 words) - 13:39, 14 March 2012
  • *** Aim at 100% -> improve CellInterface test *** improve Euler Op. test
    2 KB (278 words) - 13:59, 17 August 2007
  • ** test vrds (make sure rtstructs are printed properly) ** test image change transfer syntaxes
    1 KB (212 words) - 16:00, 9 December 2011
  • * test/CMakeList.txt
    145 bytes (19 words) - 16:00, 9 December 2011
  • * "test": testing source code (.cxx) ...se_4/Modularization/Add a module/test/CMakeLists.txt|Modules/Filtering/Foo/test/CMakeLists.txt]]
    1 KB (186 words) - 16:00, 9 December 2011
  • This page contains instructions on how to test ParaView running on a remote server or cluster. It is only a procedure for =Test setup=
    2 KB (245 words) - 21:58, 14 December 2016
  • ...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
  • ...grates a self-testing framework based on [http://www.simpletest.org Simple Test]. The self testing code is located in the ''CDash/testing'' directory. ...code from GitHub. During this step you should decide whether you want to test the latest release of CDash or the current development version.
    4 KB (665 words) - 20:38, 27 February 2017
  • # Perform an [[Git/Publish#Authentication_Test|authentication test]]:
    453 bytes (70 words) - 16:06, 9 February 2012
  • == A Test for Occlusion Spectrum Volume Rendering == ...how to use occlusion spectrum in the volume rendering process. To make the test fast, a pre-processed occlusion spectrum volume is read in from a file.
    4 KB (651 words) - 15:13, 16 August 2010
  • # Perform an [[Git/Publish#Authentication_Test|authentication test]]:
    470 bytes (71 words) - 15:51, 21 December 2011
  • ** Calling only from one test
    363 bytes (47 words) - 17:24, 25 September 2009
  • ..., Mac and Windows. The goal of these builds is to catch compile errors and test failures introduced by the topic, before the topic is merged into VTK or IT ...&showfilters=1&field1=groupname/string&compare1=61&value1=Gerrit Recurring test failures on the Gerrit builds] can easily mask new defects introduced by a
    6 KB (926 words) - 20:23, 15 February 2013
  • === Unit test === Unit test for the FEM Registration Filter
    3 KB (531 words) - 16:01, 9 December 2011
  • [ ] Test [ ] Email submission failures (this means when there are config/build/test warnings or errors)
    2 KB (335 words) - 17:56, 21 October 2011
  • ...nuous build has been reduced because there are so many ecurring continuous test failures. ...ied between 7 and 11. This effort seeks to reduce VTK Continuous recurring test failures to 0 and keep them at 0.
    8 KB (971 words) - 20:13, 15 February 2013
  • However, since test is derived from vtkObject, DATA_TYPE_NAME() is not available. How do you ca vtkTest* test = reader->GetOutput();
    5 KB (524 words) - 19:17, 26 November 2009

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