Slicer3:Testing - Revision history

Pieper: /* Tcl */

2009-12-28T23:51:51Z

Tcl

Pieper: /* Calling tests from CMake/CTest */

2009-12-28T23:45:27Z

Calling tests from CMake/CTest

Pieper at 00:26, 23 December 2009

2009-12-23T00:26:30Z

Pieper: /* Unix (linux) */

2009-11-07T20:39:30Z

Unix (linux)

Show changes

Pieper: /* Unix (linux) */

2009-11-07T20:38:54Z

Unix (linux)

Show changes

Pieper: /* Mac OSX */

2009-11-07T16:42:10Z

Mac OSX

Pieper: /* Unix */

2009-11-07T16:40:03Z

Unix

Fedorov at 21:37, 10 August 2009

2009-08-10T21:37:46Z

Nicole at 17:10, 13 May 2009

2009-05-13T17:10:03Z

Pieper: /* Unix */

2008-06-27T20:22:08Z

Unix

← Older revision		Revision as of 23:51, 28 December 2009
Line 24:		Line 24:

	== Tcl ==		== Tcl ==
		+
		+	The slicer3 tcl interpreter can be used to create tests that exercise practically the full API of the program. You can run these tests using the --script command line argument to slicer. See, for example, the tests in Slicer3/Applications/GUI/Testing [http://viewvc.slicer.org/viewcvs.cgi/trunk/Applications/GUI/Testing/]

	= Calling tests from CMake/CTest =		= Calling tests from CMake/CTest =

← Older revision		Revision as of 23:45, 28 December 2009
Line 26:		Line 26:

	= Calling tests from CMake/CTest =		= Calling tests from CMake/CTest =
		+
		+	You can add references to tests in your CMakeLists.txt file. Be sure to carefully construct the paths to work on multiple build platforms. The best way to do this is to copy an example from a working test.
		+
		+	The following example, from Slicer3/Libs/ModuleDescriptionParser/CMakeLists.txt, shows how to use the pre-defined CMake variables to find the executable and launch it in such a way that the shared libraries will be correctly defined at run time:
		+
		+	<pre>
		+	set(EXE_PREFIX ${CMAKE_RUNTIME_OUTPUT_DIRECTORY} )
		+	if(WIN32)
		+	set(EXE_PREFIX ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${CMAKE_BUILD_TYPE})
		+	endif(WIN32)
		+
		+	set(TEST_DATA ${ModuleDescriptionParserTesting_SOURCE_DIR}/TestData)
		+	add_test(Parser1Test1 ${LAUNCH_EXE} ${EXE_PREFIX}/Parser1Test ${TEST_DATA}/ParserTest1.xml)
		+	</pre>
		+
		+	In particular, note:
		+	* CMAKE_BUILD_TYPE which will be something like Release or Debug on windows and will be an empty string on mac and linux
		+	* CMAKE_RUNTIME_OUTPUT_DIRECTORY which is where the executable will be stored in the build tree
		+	* LAUNCH_EXE which is a variable optionally set by the program that uses the library you are testing. In the case of slicer3, this is set by the top-level CMakeLists.txt file to be the command line prefix to use the [[Slicer3:Launcher\|Slicer3 launcher]] to start a process with the correct environment variables defined.

	= Setting up automatic builds =		= Setting up automatic builds =

← Older revision		Revision as of 00:26, 23 December 2009
Line 1:		Line 1:
	How to do testing in Slicer3.		How to do testing in Slicer3.
		+
		+	= On the Command Line =
		+
		+	Slicer developers may want to consider running the following handy command lines before checking in code:
		+
		+	./Slicer3 --exec exit
		+
		+	(this checks that all of slicer will start and exit cleanly)
		+
		+	./Slicer3 --no-modules --exec exit
		+
		+	(this will test just the base of slicer: no modules will be loaded or built).
		+
		+	./Slicer3 --ignore-module <ModuleName> --exec exit
		+
		+	(this will specifically leave out a module to help identify where a leak or crash is coming from. Note that the module's GUI class constructor will be called, but not the BuildGUI method).

	= Writing Tests =		= Writing Tests =

← Older revision		Revision as of 16:42, 7 November 2009
Line 106:		Line 106:

	On Mac, the launchctl program is used to manage nightly builds (see [http://surfer.nmr.mgh.harvard.edu/fswiki/MacOsLaunchd Nick's excellent description from the FreeSurfer wiki]).		On Mac, the launchctl program is used to manage nightly builds (see [http://surfer.nmr.mgh.harvard.edu/fswiki/MacOsLaunchd Nick's excellent description from the FreeSurfer wiki]).
		+
		+	Here's the example .plist file for a slicer build that calls the script above every day at 4am.
		+
		+	<pre>
		+	<?xml version="1.0" encoding="UTF-8"?>
		+	<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
		+	<plist version="1.0">
		+	<dict>
		+	<key>GroupName</key>
		+	<string>slicer</string>
		+	<key>Label</key>
		+	<string>NightlyBuild</string>
		+	<key>Program</key>
		+	<string>/extra/pieper/slicer3/nightly/slicer.nightly</string>
		+	<key>ProgramArguments</key>
		+	<array>
		+	<string>&</string>
		+	</array>
		+	<key>ServiceDescription</key>
		+	<string>nightly clean build of slicer trunk</string>
		+	<key>StartCalendarInterval</key>
		+	<dict>
		+	<key>Hour</key>
		+	<integer>4</integer>
		+	<key>Minute</key>
		+	<integer>0</integer>
		+	</dict>
		+	<key>UserName</key>
		+	<string>pieper</string>
		+	</dict>
		+	</plist>
		+
		+
		+	</pre>

	== Reporting errors during genlib stage ==		== Reporting errors during genlib stage ==

@@ Line 49: / Line 49: @@
 </pre>
-== Unix ==
+== Unix (linux) ==
 Here's an example script that can be dropped into /etc/cron.daily
@@ Line 67: / Line 67: @@
 Note: the DISPLAY variable should be set to be the X display you want to run with.  Most systems will have :0 as the default display.
 Here's a similar example for a continuous build
@@ Line 85: / Line 87: @@
 * *  * * /PathToTheScriptShownJustAbove/TestSlicer3Continuous.sh
 </pre>
 == Reporting errors during genlib stage ==

← Older revision		Revision as of 17:10, 13 May 2009
Line 2:		Line 2:

	= Writing Tests =		= Writing Tests =
		+
		+	See [http://wiki.na-mic.org/Wiki/index.php/Slicer3:Execution_Model_Testing Execution Model Testing] for how to write tests for plug in modules.

	== C++ ==		== C++ ==

@@ Line 57: / Line 57: @@
 rm -rf Slicer3 Slicer3-lib Slicer3-build
-su - pieper -c "cd /home/pieper/slicer3/nightly; svn co http://www.na-mic.org/svn/Slicer3/trunk Slicer3 |& tee nightly.log"
+su - pieper -c "cd /home/pieper/slicer3/nightly; svn co http://svn.slicer.org/Slicer3/trunk Slicer3 |& tee nightly.log"
 su - pieper -c "setenv DISPLAY :0; cd /home/pieper/slicer3/nightly; ./Slicer3/Scripts/getbuildtest.tcl -t Nightly |& tee -a nightly.log"