gdave wrote:
How would I detect whether or not the object exists before I attempt the checkpoint ?
How about....
https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-activation.html
What happens if you try a Property Checkpoint keyword test on the same object?
Another possibility: You've given us the code for doing the actual checkpoint... however, what is going on immediately preceding that? The reason I ask is that the component whose property you're checking (Aliases.TransactConsole.For
Now, understandably, you can do an object spy and see the property and the object, however, in the course of running the tests, keep in mind that automation runs CONSIDERABLY faster so, when you perform an action, there may be a delay before the next step can actually be executed.
What I would do is try adding a check before your checkpoint call to WaitAliasChild on the text box. Wait for it to be present before you attempt the checkpoint. Once it comes back and is ready to be accessed, then do your check point.
Hi Marsha
I tried it as keyword test and it fails the checkpoint again.
I have attahed the word.doc with further screenshot based on keyword test.
Check my earlier response. The reason the check point is failing is because the object you are trying to access doesn't exist at the time the checkpoint code is called. There is a timing issue involved here. You need to detect whether or not the object exists before you attempt the checkpoint. The clue is in "Stub object"... that is what TestComplete passes back to something if the initial object can't be found.
How would I detect whether or not the object exists before I attempt the checkpoint ?
