Mouse movement implementation affects the TESTAR sequence flow

[ferpasri]

Current mouse movement implementation: org.fruit.Util.moveCursor(Mouse mouse, double x, double y, double duration)

Is moving the mouse from the origin coordinate to the target widget coordinate diagonally. If the mouse moves over a interactable widget which is not the target but modifies the State of the application, sequence flow will be altered.

For the creation of the State Model this issue is even worse because it affects the generation of model transitions and model determinism.

Reproducible example: SUT: Notepad Time settings -> Action duration -> 1 sec (Visible mouse debug) Filter all Notepad widgets except "View -> Zoom -> Zoom.." flow

[pekkakaho]

For menus on top of the screen, we could move mouse first down and then right/left, but that might be a problem for other kind of widgets that require a click to open another widget.