Documentation/Nightly/Developers/QtTesting - Revision history

JChris.FillionR: /* Overview */

2022-04-26T19:34:09Z

Overview

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

2019-11-27T02:22:38Z

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

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

2013-06-14T07:57:12Z

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

Finetjul: /* Create your XML script */

2012-06-25T20:57:57Z

Create your XML script

BenjaminLong: /* How QtTesting and CTK work */

2012-06-25T20:04:27Z

How QtTesting and CTK work

BenjaminLong: /* How QtTesting and CTK work */

2012-06-25T20:01:15Z

How QtTesting and CTK work

BenjaminLong: /* How QtTesting and CTK work */

2012-06-25T19:54:39Z

How QtTesting and CTK work

BenjaminLong: /* How QtTesting and CTK work */

2012-06-25T19:50:23Z

How QtTesting and CTK work

BenjaminLong at 19:47, 25 June 2012

2012-06-25T19:47:08Z

JChris.FillionR at 05:10, 17 June 2012

2012-06-17T05:10:19Z

@@ Line 7: / Line 7: @@
 |}
 =Overview=
 QtTesting provides us a testing framework to test our application. It complements unit tests, by testing the application in its globality.

@@ Line 50: / Line 50: @@
 == Create your XML script ==
-See [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/SlicerApplication/QtTesting QtTesting user Wiki] to know how to create this xml script.<br>
+See [[Documentation/Nightly/SlicerApplication/QtTesting|QtTesting user Wiki]] to know how to create this xml script.<br>
 '''Save the xml script to''' <code>Slicer/Applications/SlicerApp/Data/Input/MYTUTORIALNAME.xml''</code><br>
 {{ambox
 | type = content
-|text = If you need data, please first add the data to the Sample Data module, and use this module during the test. See instruction [http://www.slicer.org/slicerWiki/index.php/SampleData here]<br>
+|text = If you need data, please first add the data to the Sample Data module, and use this module during the test. See instruction [[SampleData|here]]<br>
 [[Documentation/{{documentation/version}}/Modules/SampleData Sample Data]] module according to the current Slicer version
 }}

← Older revision		Revision as of 07:57, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	{\|width="100%"		{\|width="100%"
	\|		\|

@@ Line 53: / Line 53: @@
 {{ambox
 | type = content
-|text = If you needs data, please first add the data to the Sample Data module, and use this module during the test. See instruction [http://www.slicer.org/slicerWiki/index.php/SampleData here]<br>
+|text = If you need data, please first add the data to the Sample Data module, and use this module during the test. See instruction [http://www.slicer.org/slicerWiki/index.php/SampleData here]<br>
 [[Documentation/{{documentation/version}}/Modules/SampleData Sample Data]] module according to the current Slicer version
 }}

@@ Line 24: / Line 24: @@
 {|width="100%"
 |align="left"|
-[[Image: ctkQtTestingSchemaPlay.png|600px|]]
+[[Image: ctkQtTestingSchemaPlay.png|550px|]]
-|align="right"|
+|align="left"|
-[[Image: ctkQtTestingSchemaRecord.png|600px]]
+[[Image: ctkQtTestingSchemaRecord.png|550px]]
 |-
 |'''''How it works :'''''

← Older revision		Revision as of 19:50, 25 June 2012
Line 21:		Line 21:

	=How QtTesting and CTK work=		=How QtTesting and CTK work=
		+
		+	{\|width="100%"
		+	\|align="left"\|
		+	[[Image: ctkQtTestingSchemaPlay.png]]
		+	\|align="right"\|
		+	[[Image: ctkQtTestingSchemaRecord.png]]
		+	\|}

	=Write a 3DSlicer test using QtTesting=		=Write a 3DSlicer test using QtTesting=

← Older revision		Revision as of 19:47, 25 June 2012
Line 19:		Line 19:

	* Use '''''"activated"''''' signal instead of '''''"clicked"''''', when connection Qt views		* Use '''''"activated"''''' signal instead of '''''"clicked"''''', when connection Qt views
		+
		+	=How QtTesting and CTK work=

	=Write a 3DSlicer test using QtTesting=		=Write a 3DSlicer test using QtTesting=

@@ Line 22: / Line 22: @@
 =Write a 3DSlicer test using QtTesting=
-QtTesting framework can also be use to create module test.<br> Use the description below, but instead of <code>Slicer4/Applications/SlicerApp/Testing</code> all the path start by <code>Slicer4/Path/To/The/Modules/Testing</code>
+QtTesting framework can also be use to create module test.<br> Use the description below, but instead of <code>Slicer/Applications/SlicerApp/Testing</code> all the path start by <code>Slicer/Path/To/The/Modules/Testing</code>
 Following is the different step to create a test using QtTesting framework.
@@ Line 28: / Line 28: @@
 == Create your XML script ==
 See [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/SlicerApplication/QtTesting QtTesting user Wiki] to know how to create this xml script.<br>
-'''Save the xml script to''' <code>Slicer4/Applications/SlicerApp/Data/Input/MYTUTORIALNAME.xml''</code><br>
+'''Save the xml script to''' <code>Slicer/Applications/SlicerApp/Data/Input/MYTUTORIALNAME.xml''</code><br>
 {{ambox
 | type = content
@@ Line 49: / Line 49: @@
        raise Exception('Failed to finished properly the play back !')
-'''''Save to the directory ''''' <code>Slicer4/Applications/SlicerApp/Testing/Python/MYTUTORIALNAME.py </code>
+'''''Save to the directory ''''' <code>Slicer/Applications/SlicerApp/Testing/Python/MYTUTORIALNAME.py </code>
 == Add the test in CMake ==
 Adding the test in CMake will allow the test to be run with CTest and will also be run by the dashboard machines every nights.
-Edit the file <code>Slicer4/Applications/SlicerApp/Testing/Python/CMakeLists.txt</code><br>
+Edit the file <code>Slicer/Applications/SlicerApp/Testing/Python/CMakeLists.txt</code><br>
 Add your test at the end of the Slicer_USE_QTTESTING condition and add the name in the <code>set_tests_properties</code> function :
@@ Line 88: / Line 88: @@
 | colspan=2; valign="top" |
 You need to open a terminal.<br>Then type in the terminal:<br><br>
-  $ cd path/to/Slicer4-Superbuild/Slicer-build
+  $ cd path/to/Slicer-Superbuild/Slicer-build
   $ ctest -R MYTUTORIALNAME -VV
 | valign="top" |
@@ Line 94: / Line 94: @@
 Start -> Microsoft Visual Studio 2008 -> Visual Studio Tools -> Visual Studio 2008 Command Prompt<br>
 Then type in the terminal:<br>
-  $ cd path\to\Slicer4-Superbuild\Slicer-build
+  $ cd path\to\Slicer-Superbuild\Slicer-build
   $ path\to\cmake\ctest.exe -R MYTUTORIALNAME -VV
 |}
@@ Line 106: / Line 106: @@
 | colspan=2; valign="top" |
 You need to open a terminal.<br>Then type in the terminal:<br><br>
-  $ cd path/to/Slicer4/Application/SlicerApp/Testing/Python
+  $ cd path/to/Slicer/Application/SlicerApp/Testing/Python
   $ python MYTUTORIALNAME.py
 | valign="top" |
@@ Line 112: / Line 112: @@
 Start -> Microsoft Visual Studio 2008 -> Visual Studio Tools -> Visual Studio 2008 Command Prompt<br>
 Then type in the terminal:<br>
-  $ cd path\to\Slicer4\Applicaiton\SlicerApp\Testing\Python
+  $ cd path\to\Slicer\Applicaiton\SlicerApp\Testing\Python
-  $ path\to\Slicer4-Superbuild\python-build\PCBuild\python.exe MYTUTORIALNAME.py
+  $ path\to\Slicer-Superbuild\python-build\PCBuild\python.exe MYTUTORIALNAME.py
 |}
@@ Line 130: / Line 130: @@
 | colspan=2; valign="top" |
 You need to open a terminal.<br>Then type in the terminal:<br><br>
-  $ cd path/to/Slicer4-Superbuild/CTK-build/QtTesting/Utilities/Scripts
+  $ cd path/to/Slicer-Superbuild/CTK-build/QtTesting/Utilities/Scripts
   $ python TranslatorPlayerWizard.py MY_WIDGET_NAME
   $ cd ../MY_WIDGET_NAME
@@ Line 137: / Line 137: @@
 Start -> Microsoft Visual Studio 2008 -> Visual Studio Tools -> Visual Studio 2008 Command Prompt<br>
 Then type in the terminal:<br>
-  $ cd path\to\Slicer4-Superbuild
+  $ cd path\to\Slicer-Superbuild
   $ python-build\PCBuild\python.exe CTK-build\QtTesting\Utilities\Scripts\TranslatorPlayerWizard.py MY_WIDGET_NAME
   $ cd ../MY_WIDGET_NAME
@@ Line 153: / Line 153: @@
 Finally move the 4 files to the same directory as your widget
-  $ cd path/to/Slicer4-Superbuild/CTK-build/QtTesting/Utilities/MY_WIDGET_NAME
+  $ cd path/to/Slicer-Superbuild/CTK-build/QtTesting/Utilities/MY_WIDGET_NAME
   $ mv MY_WIDGET_NAMETranslator.cpp MY_WIDGET_NAMETranslator.h MY_WIDGET_NAMEPlayer.cpp MY_WIDGET_NAMEPlayer.h Path/To/My/Widget/Directory