Documentation/Widget testing: Difference between revisions
From Commontk
Jump to navigationJump to search
Line 212: | Line 212: | ||
|{{Done}}{{Doing}} | |{{Done}}{{Doing}} | ||
| | | | ||
|''QSpin issue + Name QSpin issue : EventTranslator ?'' | | bgcolor="#efabab" |''QSpin issue + Name QSpin issue : EventTranslator ?'' | ||
|- | |- | ||
|ctkMenuButton | |ctkMenuButton | ||
Line 222: | Line 222: | ||
|{{Doing}}{{Not Done}} | |{{Doing}}{{Not Done}} | ||
|'''+++''' | |'''+++''' | ||
|''Implemented Event Translator/Player '' | | bgcolor="#efabab" |''Implemented Event Translator/Player '' | ||
|- | |- | ||
|ctkModalityWidget | |ctkModalityWidget |
Revision as of 16:25, 20 October 2011
Home < Documentation < Widget testingOverview
Testing of both CTK widgets and application built on top of CTK could leverage the capabilities offered by the QtTesting library developed by Paraview folks.
If the option CTK_USE_QTTESTING is enabled, the build system will:
- Download external project QtTesting
- Include the event translator and player required for custom CTK widgets. (Located in the same folder as their associated widget sources)
- Include the class ctkEventTranslaterPlayerWidget into CTKWidgets library
- If BUILD_TESTING is enabled: CTK widgets EventTranslatorTests will be compiled. These tests will use ctkEventTranslaterPlayerWidget and ensure that events associated with CTK widgets can be properly recorded and played.
Note: Option CTK_USE_QTTESTING will be automatically enabled if BUILD_TESTING is ON
Milestones
- Integration: What and where.
- Integrate QtTesting has an external projects
- Implement ctkEventTranslaterPlayerWidget
- Create custom translator/player if needed
- Implement widgets EventTranslatorTests