Documentation/Widget testing: Difference between revisions
From Commontk
Jump to navigationJump to search
Line 579: | Line 579: | ||
= Issues found on QtTesting = | = Issues found on QtTesting = | ||
* QSpinBox/QDoubleSpinBox : | *''' QSpinBox/QDoubleSpinBox :''' | ||
** A long click on the up/down arrow -> just one click even if the value change severals times | ** A long click on the up/down arrow -> just one click even if the value change severals times. | ||
** Fast click -> Double click -> no effect. | ** Fast click -> Double click -> no effect. | ||
** clik on the up/down arrow just after editing the spin Box -> no effect. | |||
''Solve : Contribution to the QtTesting by modified the pqSpinBoxEventTranslator'' {{Doing}} - Push on my local branch - | |||
* In pq3DView : | *''' In pq3DView :''' | ||
** The scroll button has no effect - Implemented for ctk | ** The scroll button has no effect - Implemented for ctk. | ||
** Shift between the current/Expected image. | |||
''Solve : new Implementation with the ctkVTKRenderViewEventTranslator and the ctkVTKRenderViewEventPlayer :'' {{Done}} | |||
# ''Change the normalization into a normalization by the widget center.'' | |||
# ''Implemented the scroll action'' | |||
# ''Add a better rounded when we cast from double to int to not have shift issue.'' | |||
* QComboBox when it is editable : | |||
*''' QComboBox when it is editable :''' | |||
** The hight-event "set_sting" crash if we edit the comboBox. | ** The hight-event "set_sting" crash if we edit the comboBox. | ||
*** '''''Exemple :''' If we have an item "foo", we are going to edit the comboBox with "f", but the item "f" doesn't exist, and the player will crash.'' | *** '''''Exemple :''' If we have an item "foo", we are going to edit the comboBox with "f", but the item "f" doesn't exist, and the player will crash.'' | ||
''Solve : ...'' {{Not Done}} | |||
= Screenshots = | = Screenshots = |
Revision as of 14:40, 25 November 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
- Integrate QtTesting has an external projects
- Add unit test to all the widget - Below, the summuray table -
- Create an Application test - ctkQtTesting -
Player/Translators Widget Testing
Issues found on QtTesting
- QSpinBox/QDoubleSpinBox :
- A long click on the up/down arrow -> just one click even if the value change severals times.
- Fast click -> Double click -> no effect.
- clik on the up/down arrow just after editing the spin Box -> no effect.
Solve : Contribution to the QtTesting by modified the pqSpinBoxEventTranslator - Push on my local branch -
- In pq3DView :
- The scroll button has no effect - Implemented for ctk.
- Shift between the current/Expected image.
Solve : new Implementation with the ctkVTKRenderViewEventTranslator and the ctkVTKRenderViewEventPlayer :
- Change the normalization into a normalization by the widget center.
- Implemented the scroll action
- Add a better rounded when we cast from double to int to not have shift issue.
- QComboBox when it is editable :
- The hight-event "set_sting" crash if we edit the comboBox.
- Exemple : If we have an item "foo", we are going to edit the comboBox with "f", but the item "f" doesn't exist, and the player will crash.
- The hight-event "set_sting" crash if we edit the comboBox.