Hi luisanillo,
Also, I would recommend that you read the Monitoring Tested Application Performance article. I think it should help you better understand what is happening on the computer during the test run.
I'm not sure any of us schmo users will be able to answer that question. There is no "frequency" setting but you have to assume that it is often enough and rapid enough to return a result quickly.
As for "Exists"... I would not use WaitProperty for Exists. Think about it... how do you call the WaitProperty method on an object that does not exist and, therefore, does not have a WaitProperty method?
Waiting for existance is better done with a WaitChild, WaitAliasChild, or other similar "Wait" method that actually waits for the object. You can also use Find, FindEx, FindChild, and FindChildEx.
The object was mapped before hand, so I'm assuming that it knows of it. By waiting for exists, I know that once it's property is set to true, it will be visible.
You may ask why not check for visible, and it is because it fails, since the object does not exists and thus, does not contain a proprerty visible yet.
For you answer about the frequency, I assumed it was quick, but that is the problem. This operation takes around 1 to 2 hours. Imagine querying that property, let's say, 3 times per second. That will surely slow down the whole system, and thus, explain why my results are over what I obtain in manual testing.
Edit: about WaitChild and others, will it do the same as WaitProperty but for an object ? By reading the documentation, I have a feeling that yes it does, therefore, my question still applies; at what frequency and how do I change it ?
Thanks for showing interest in my question!
Mapped <> Exists. Existance has to do with whether or not the object exists in your machine's memory. That's what WaitChild and WaitAliasChild do.
This is the better way of checking existance
var myParentObject = Aliases.MyApp.MyParent
if ((myParentObject.WaitAliasChild('MyChildObject', 1000).Exists) {
Log.Message("My object exists within 1 second")
}
Else {
Log.Message("My object was not present in memory after 1 second")
}
Using WaitProperty means you're putting TestComplete through the cycle of trying to find first of all find the object whose property you're checking before it can call the WaitProperty method.
As for frequency... I don't know... I'm just a user... but I do know that there's no way in code or settings to change it. Sorry.
