Difference between revisions of "Documentation/Nightly/SlicerApplication/QtTesting"
m |
|||
Line 29: | Line 29: | ||
[[Image: QtTestingSettigns.png |450px]] | [[Image: QtTestingSettigns.png |450px]] | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Recorder== | ==Recorder== | ||
Line 91: | Line 69: | ||
* '''Info tab''' : | * '''Info tab''' : | ||
** Show the last event played. | ** Show the last event played. | ||
+ | |||
+ | ===Default settings recorded=== | ||
+ | To limit playback problems, QtTesting records automatically some of the applications settings. | ||
+ | * General settings : | ||
+ | ** The application's geometry | ||
+ | ** The application's state | ||
+ | ** The application's name | ||
+ | ** The application's version | ||
+ | |||
+ | * 3DSlicer settings : | ||
+ | ** The current layout | ||
+ | ** The current module | ||
+ | |||
+ | Before each play back, if these settings are currently different, QtTesting asks if you want to restore the settings to the record application state. <br> | ||
+ | {{ambox | ||
+ | | type = speedy | ||
+ | | small = left | ||
+ | | text = It's strongly recommended to accept ! | ||
+ | }} | ||
|align="right"| | |align="right"| | ||
Line 99: | Line 96: | ||
==User limitations== | ==User limitations== | ||
− | ''QtTesting in 3DSlicer is still under development, and some events | + | ''QtTesting in 3DSlicer is still under development, and some events might not be recorded properly.'' |
'''Following what is subject to not work :''' | '''Following what is subject to not work :''' |
Revision as of 21:01, 24 May 2012
Home < Documentation < Nightly < SlicerApplication < QtTestingOverview
QtTesting is an effort started by ParaView team Paraview Wiki |
Too lazy to do the same actions over and over? QtTesting is the answer! The QtTesting library provides you with an easy way to record and play macros with 3DSlicer. Included in this library is a user-friendly recording interface that shows you what actions you're recording as well as a simple and smart playback interface that will allow you to control actions whenever you want. With no input from the user, QtTesting record all accomplished actions from the point you have started the record until you stop it! "Create a puppet and let it do the rest ... "
Slicer developers already use this library to record tutorials and test Slicer3D application.
Activate QtTesting
By default, QtTesting is not activated. You must enable it to be able to record or play a saved macro.
|
Recorder
Recording a macro consists in observing all the high level events (or low level in some cases) that the user generate by interacting with the GUI elements. All the events are saved into a file (.xml) that can be used later to replay the recorded events in the same or different instance of the Slicer application.
Start recording
A record dialog appears at the bottom left of the application Record dialog
Save macro
|
Player
Recorded macros (.xml) can be replayed within Slicer sessions. Note that the success of the macro execution can depend on the original state of the application.
How to Start
Player dialog
Default settings recordedTo limit playback problems, QtTesting records automatically some of the applications settings.
Before each play back, if these settings are currently different, QtTesting asks if you want to restore the settings to the record application state.
|
User limitations
QtTesting in 3DSlicer is still under development, and some events might not be recorded properly.
Following what is subject to not work :
- Some actions under submenu, mainly actions on widget.
work not perfectly:
- A shift appear when you are using the 3D interactor.