Documentation/Nightly/Developers/Tutorials/SelfTestModule - Revision history

Grundlett: Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2"

2019-11-27T02:30:19Z

Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2"

2018-12-08T07:27:30Z

2016-04-29T13:41:13Z

Creating the Skeleton

2014-03-26T14:57:42Z

Goal: fix wrong-version link

2013-09-27T22:06:44Z

Use the ModuleWizard

2013-09-25T16:24:42Z

Writing/Refining the Code

2013-06-14T07:59:09Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2012-10-17T21:00:20Z

Test Data

2012-09-25T19:20:53Z

Test Data

2012-09-12T22:00:45Z

Writing/Refining the Code

@@ Line 81: / Line 81: @@
 Save the file and click Reload and Test.  You should see your new message as a dialog and you should also see it printed in the console.
-From here, you "only" need to implement the python code that performs your test.  For that, you can rely on the python wrappings of Qt, VTK, numpy, etc. [http://www.slicer.org/slicerWiki/index.php/Slicer4:Python Python in Slicer4]
+From here, you "only" need to implement the python code that performs your test.  For that, you can rely on the python wrappings of Qt, VTK, numpy, etc. [[Slicer4:Python|Python in Slicer4]]
 To open up the GUI for a specific module, for instance the Volumes modules, you can use:

@@ Line 6: / Line 6: @@
 Important features include:
 * Tests are available as part of the binary distributions of slicer, so users can confirm correct behavior on their systems
-* The same tests are run as part of the nightly test process and submitted to [http://slicer.cdash.org/index.php?project=Slicer4 the slicer dashboard].
+* The same tests are run as part of the nightly test process and submitted to [http://slicer.cdash.org/index.php?project=SlicerPreview the slicer dashboard].
 * Developers can efficiently develop the tests by reloading python scripts without needing to exit slicer.

@@ Line 24: / Line 24: @@
 === Use the ModuleWizard ===
-Start by using the [[Documentation/{{documentation/version}}/Developers/ModuleWizard|module wizard]] to create a new scripted module.
+Start by using the [[Documentation/{{documentation/version}}/Developers/ExtensionWizard|extension wizard]] to create a new scripted module.
 Give the module a descriptive name based on the functionality you intend to test.  If the module is created to recreated the steps described in a bug report, append the bug report name to the end of the test.  For example, one test is [http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Applications/SlicerApp/Testing/Python/sceneImport2428.py?view=markup sceneImport2428.py] which tests [http://www.na-mic.org/Bug/view.php?id=2428 issue #2428].
 === Edit the new module ===

@@ Line 14: / Line 14: @@
 * When developing a new scripted module, you can create a test script at the same time.  This way you can use the script to help you test the code as you develop it (by reloading and testing as you write the code without even exiting slicer) and also verify that your code still works as you refactor and improve the code.  Plus, you can easily test the code on multiple platforms without a lot of tedious clicking to reload data.
 * Self Tests of the core slicer functionality can be used equally in build-time and run-time scenarios.
-* [[Documentation/4.1/Developers/Modules|Any type of module or extension]] can also include self tests (and should!).
+* [[Documentation/{{documentation/version}}/Developers/Modules|Any type of module or extension]] can also include self tests (and should!).
 == Caveats ==

@@ Line 31: / Line 31: @@
   cd <Slicer source dir>
-  ./Utilities/Scripts/ModuleWizard.py --template ./Extensions/Testing/ScriptedLoadableExtensionTemplate --target ../NeurosurgeryTutorial NeurosurgeryTutorial
+  ./Utilities/Scripts/ModuleWizard.py --template ./Extensions/Testing/ScriptedLoadableExtensionTemplate/ScriptedLoadableModuleTemplate --target ../NeurosurgeryTutorial NeurosurgeryTutorial
 This will create a new extension directory with a skeleton NeurosurgeryTutorial.py file ready to work on.

@@ Line 95: / Line 95: @@
      m.moduleSelector().selectModule('Volumes')
      self.delayDisplay("Entered Volumes module")
 == Adding the Result to Slicer ==

← Older revision		Revision as of 07:59, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	== Goal ==		== Goal ==

← Older revision		Revision as of 21:00, 17 October 2012
Line 66:		Line 66:

	[http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Applications/SlicerApp/Testing/Python/ other self test scripts] load multiple datasets and/or scene files.		[http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Applications/SlicerApp/Testing/Python/ other self test scripts] load multiple datasets and/or scene files.
		+
		+	Note that the current test template will re-use any existing file in the temp directory that has non-zero size. If you change the test data, give it a new name for the download.

	=== Accessing Test Data Through A Firewall ===		=== Accessing Test Data Through A Firewall ===

← Older revision		Revision as of 19:20, 25 September 2012
Line 67:		Line 67:
	[http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Applications/SlicerApp/Testing/Python/ other self test scripts] load multiple datasets and/or scene files.		[http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Applications/SlicerApp/Testing/Python/ other self test scripts] load multiple datasets and/or scene files.

		+	=== Accessing Test Data Through A Firewall ===
		+
		+	The SelfTest modules use python urllib to download data. If you are behind a firewall, you can configure urllib to use a proxy server by setting the environment variable
		+
		+	export http_proxy=http://proxyhost:proxyport
		+
		+	Note the use of "http://" at the start of the url. The environment variable http_proxy is also used by git and wget but they do not require the "http://" but will accept it if there.

	== Writing/Refining the Code ==		== Writing/Refining the Code ==