Difference between revisions of "Documentation/Nightly/Developers/QtTesting"

From Slicer Wiki
Jump to: navigation, search
Line 68: Line 68:
 
|}
 
|}
  
4 files should have been created ! <br>  
+
{{ambox
 +
| type = speedy
 +
| text = 4 files should have been created ! <br>  
 
<code>MY_WIDGET_NAMETranslator.cpp <br>  
 
<code>MY_WIDGET_NAMETranslator.cpp <br>  
 
MY_WIDGET_NAMETranslator.h <br>  
 
MY_WIDGET_NAMETranslator.h <br>  
 
MY_WIDGET_NAMEPlayer.cpp <br>  
 
MY_WIDGET_NAMEPlayer.cpp <br>  
MY_WIDGET_NAMEPlayer.h</code>
+
MY_WIDGET_NAMEPlayer.h</code><br>Those files are only the basic code. You now have to implement the functions, according to your widget, to record the events
 
 
{{ambox
 
| type = speedy
 
| text = Those files are only the basic code. You now have to implement the functions, according to your widget, to record the events
 
 
}}
 
}}
  

Revision as of 18:16, 24 May 2012

Home < Documentation < Nightly < Developers < QtTesting

Overview

Write a 3DSlicer UnitTest with QtTesting

1/ Create your XML script

See QtTesting user Wiki

2/ Create a Python script

This Python test will start 3DSlicer and run the previously recorded xml script

Create a file with the following code

   import slicer
   import slicer.testing
   import slicer.util
   filepath = os.environ['SLICER_HOME'] + 'path/to/your/script.xml'
   testUtility = slicer.app.testingUtility()
   success = testUtility.playTests(filepath)
   if success :
       slicer.util.exit(EXIT_SUCCESS)
   else:
       slicer.util.exit(EXIT_FAILURE)

Save to the directory ${Slicer_SOURCE_DIR}/Applications/SlicerApp/Testing/Python/

3/ Add the test in CMake

Edit the file Slicer4/Applications/SlicerApp/Testing/Python/CMakeLists.txt

Add your test at the end of the Slicer_USE_QTTESTING condition:

   if(Slicer_USE_QTTESTING)
     {   
     ...
     slicer_add_python_test(
       SCRIPT pythonScriptName.py
       SLICER_ARGS --launcher-no-splash --qt-testing)
     }


You just wrote a Slicer Unit Test using QtTesting framework !

Create custom translator/player

QTTesting provides us basic translator and player template.
You can use the following command to create those basic files.

Linux Mac Windows

You need to open a terminal and go to the Slicer4 source directory.
Then type in the terminal:

$ cd path/to/Slicer4-Superbuild/CTK-build/QtTesting/Utilities/Scripts
$ python TranslatorPlayerWizard.py MY_WIDGET_NAME
$ cd ../MY_WIDGET_NAME

You need to open a terminal and go to the Slicer4 source directory.
Start -> Microsoft Visual Studio 2008 -> Visual Studio Tools -> Visual Studio 2008 Command Prompt
Then type in the terminal:

$ cd path\to\Slicer4-Superbuild
$ python-build\PCBuild\python.exe CTK-build\QtTesting\Utilities\Scripts\ModuleWizard.py MY_WIDGET_NAME
$ cd ../MY_WIDGET_NAME

Open bugs

Work in progress, following the two bug trackers :

Slicer issues

QtTesting issues