the application enough time to respond to the issued events.
For instance, consider a test that involves opening a menu
by clicking on it with the mouse, and then clicking on a
menu item. When performing this task automatically using
a tool that issues X events, the developer must insert a delay
between the two automated click events. After the first click
on the menu, the second click must be delayed until the
tested application can open and display the menu on the
screen. This technique works well for simple automation
tasks, but for runtime measurements, long delays can easily
mask the incurred overhead and lead to inaccurate results.
Taking this into consideration, in our tests, we refrained from
using any artificial delays, or employing tools that operate
in this way.
the application enough time to respond to the issued events.
For instance, consider a test that involves opening a menu
by clicking on it with the mouse, and then clicking on a
menu item. When performing this task automatically using
a tool that issues X events, the developer must insert a delay
between the two automated click events. After the first click
on the menu, the second click must be delayed until the
tested application can open and display the menu on the
screen. This technique works well for simple automation
tasks, but for runtime measurements, long delays can easily
mask the incurred overhead and lead to inaccurate results.
Taking this into consideration, in our tests, we refrained from
using any artificial delays, or employing tools that operate
in this way.
การแปล กรุณารอสักครู่..
