Are you using name mapping or FindChild to locate your objects?
nameMapping
It sounds like you don't have all of that frame mapped yet. If you take ObjectSpy and look at one of those fields, can you trace back to the Object Tree and then from there back to the Name Mapping Editor?
Thank you for your reply. I did take ObjectSpy and look at the object that I want to click, I can trace back to the Object Tree and then back to the Name Mapping Editor. I am not sure if it is the nameMapping issue or the iFrame the has lots of tables inside. But if I run the test again from the selected operation(which is the point that made the test failed at the first place) , the test would pass.
Here the error messages from test log:
The object does not exist. See Additional Information for details.
There was an attempt to perform an action at point (0, 0) which is transparent or out of the window bounds.
A clue! A clue! (forgive the retro children's show reference)
If your test will proceed from there correctly, then it's likely you have a timing issue. The test is moving faster than the object is loading so it is Not Found when the test goes but when you click and keep it running it's Found.
There are some different ways to go to fix this.
1) You can put a Delay right before the line that gets the object not found message. This is a quick fix but you have to guess at how long to wait, just long enough but not so long that it delays your whole test. Usually 5000 or 10000 will fix it but it's not very precise.
2) If you know that the object in question should always show up, then use some variation of WaitChild to wait for the object to show up before you try to do anything with it.
If you find that this is happening to you in many places in your tests, then considering slowing down the time between events in your project settings. This will slow the whole test down some, but it is more efficient than trying to change it every where in the code.
