Opened 12 years ago
Closed 12 years ago
#11982 closed defect (fixed)
Robot timing errors
Reported by: | haysmark | Owned by: | Douglas Hays |
---|---|---|---|
Priority: | high | Milestone: | 1.6 |
Component: | TestFramework | Version: | 1.5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
The doh.robot schedulers assume real-time processing. The reality is that people run tests on clouds, virtual machines, slow computers, and slow browsers where real-time processing is not guaranteed. We should try to adjust the schedule as robot actions fire to compensate for unexpected lag.
Attachments (2)
Change History (5)
Changed 12 years ago by
Attachment: | 11982.patch added |
---|
comment:1 Changed 12 years ago by
Owner: | changed from alex to Douglas Hays |
---|
comment:2 Changed 12 years ago by
Milestone: | tbd → 1.6 |
---|
Some of the sequence durations are still being doubled due to a new sequence call coming in just before the previous duration setTimeout fires. I suggest the following sequence function replacement:
var currentTime = (new Date()).getTime(); if(currentTime > (doh.robot._time || 0)){ doh.robot._time = currentTime; } doh.robot._time += delay || 1; setTimeout(f, doh.robot._time - currentTime); doh.robot._time += duration || 0;
comment:3 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Refs #11982. Modify doh.robot scheduling of typeKeys and mouseMove to compensate for unexpected delays.