Difference between revisions of "AHM2009:GUI Testing"
From NAMIC Wiki
| Line 10: | Line 10: | ||
* How to add Squish tests using CMake macros, so that they can be run nightly from ctest. | * How to add Squish tests using CMake macros, so that they can be run nightly from ctest. | ||
* Squish current known issues with some KWWidgets. | * Squish current known issues with some KWWidgets. | ||
| + | ** vtkKWComboBox, vtkKWMenuButton | ||
| + | ** Recording a lot of MouseMove events with coordinates, which may not always be reliable. | ||
| + | ** Asynchronous handling of mouse events, which is difficult to control of the procedure-flow, so in some cases, manual insert of "wait-some-time" is needed in the script | ||
| + | ** RenderWindow mouse move events are recorded and played back TOO MUCH. | ||
| + | |||
* Discussions: tests validation methods. | * Discussions: tests validation methods. | ||
Revision as of 06:01, 18 December 2008
Home < AHM2009:GUI TestingBack to AHM_2009
Breakout session Moderator: Sebastien Barre
Introduction: Automatic KWWidgets and Slicer GUI Testing
Agenda:
- How to create Squish test suites from Squish IDE.
- How to add validation points in Squish tests.
- How to add Squish tests using CMake macros, so that they can be run nightly from ctest.
- Squish current known issues with some KWWidgets.
- vtkKWComboBox, vtkKWMenuButton
- Recording a lot of MouseMove events with coordinates, which may not always be reliable.
- Asynchronous handling of mouse events, which is difficult to control of the procedure-flow, so in some cases, manual insert of "wait-some-time" is needed in the script
- RenderWindow mouse move events are recorded and played back TOO MUCH.
- Discussions: tests validation methods.
