Variable delay time

Your application would have some properties indicated that some event was successfully fired (e.g. data base was updated or file was uploaded). The common approach looks like:

application.UpdateDatabase()

flag = application.WaitProperty(PropertyName, PropertyValue, WaitTime) 

if flag:
    doSomething
else:
    doSomethingElse

Wait Property() method returns True or False. 

Also you can use WaitChild() method, which returns the object of your application or the Null value.

Or you can hard-code your delay using aqUtils.Delay(timeout), where timeout is your variable (in milliseconds).

---

r_ahmakov wrote:

Hi ,

 

For some faster and smaller tests I'd like to reduce these delays in the entire test...or when the test is running on faster laptop.

 

Something like that will be perfect :)

 

TestDelay = Delay()*VariableParameter

 

 

---

You can easily create a variable at the Project or ProjectSuite level and then reference that variable within your delay statements... which will get you through this first hurdle, but there will be times that this fails unless you set the timeout delays high enough to pass on the slowest machines.

Eventually you'll want to perform (or rather your bosses will want you to perform) some real synchronization.

Here's an example of logic I use when waiting for a file to download.

1. Click the download button (or link or whatever)
2. Start a loop (that does the next two steps over and over again)
3. Delay 5000ms (5 seconds)
4. Check to see if the file is present in the specific dwonload directory
5. If not present, increment a counter and wait another 5 seconds
   • If the file is present, drop out of the loop and continue on with the test
6. After looping/waiting for about 60 seconds (or however long you think is appropriate), drop out of the loop and log an error stating that the file was not found. (then you can go back and manually verify why the file hasn't completely downloaded after the 60 seconds)

This logic stuff is a little more difficult, but A LOT more reliable. My tests can run at any hour of the day or night and the looping logic addresses any network latency or internet slow-downs... and doesn't cause me to wait for 60 seconds with each download. The longest you're waiting is an extra 5 seconds if the file is is present immediately after checking for its existence (decreasing the 5000ms delay also resolves that issue if you're concerned).

Good luck!