Using HISUtils.StopWatch in keyword tests
I want to open this out to others to see if there's anyone else who has a better way of doing this. Essentially, the goal is to minimize, as much as possible, the amount of script code that nee...
Forum Discussion
Hi,
I have just created a working test with the WaitProperty. However, what we have noticed sofar, is that it takes about 2-3 seconds for TestComplete to recognize that the Visible property of the object is true. Meaning that the test results are "poluted" with 2-3 seconds. The window appears after about 4 seconds, but TC's Stopwatch results tells us about 7 seconds.
Do you know why this 2 seconds delay comes from? (perhaps because of the namemapping tree which needs to be updated?)
Is there another, more precise approach, to time more accurately?
Please advice.
Thanks,
Mathijs
I have just created a working test with the WaitProperty. However, what we have noticed sofar, is that it takes about 2-3 seconds for TestComplete to recognize that the Visible property of the object is true. Meaning that the test results are "poluted" with 2-3 seconds. The window appears after about 4 seconds, but TC's Stopwatch results tells us about 7 seconds.
Do you know why this 2 seconds delay comes from? (perhaps because of the namemapping tree which needs to be updated?)
Is there another, more precise approach, to time more accurately?
Please advice.
Thanks,
Mathijs
