Did you have a chance to get a stack trace on timeout? The change in the
tests are correct but it is unclear in what place the test may hang and
why the changes fixed it.
On 13/02/2018 01:22, Prasanta Sadhukhan wrote:
Please review a testfix seen in the recent sprint-run, whereby the test
seems to times out .
Seems like test is issuing mouse events without waiting for robot to
process those events.
Enhance the test to allow robot to process the events and also dispose
of the frame once done,
so it should not bother other tests when run in bunch.
Best regards, Sergey.