I've an issue with accessing some objects during testing. My application is a .NET WinForms GUI one that uses WebServices to connect with server. When application needs to refresh more data TestComplete couldn't access to some WinForms objects. It's random issue and happens in different places in code.
The problem is that when I manually use the application after testing I notice no performance issues.
Maid it be an TestComplete issue? Maybe TestComplete has some bugs that occur after long term testing? How to determine what is my problem: either tested application or TestComplete.
Please help and save months of my work,
Thanks in advance.
This sounds like a timing issue occurring at the places where you are trying to access the objects. TestComplete executes scripts at "robot" speed so that, unless you specify, it will assume that objects, components, etc, are immediately available.
Without seeing your script code, what it sounds like you might need to do is inject code to "wait" for components and such. Research the "WaitWinFormsObject" method in TestComplete for more information for your particular need. Hardcoded delays are also possible but I would steer away from those because there is ambiguity at times as to how long to wait for something (as evidenced by your "random" issue).
Automated Testing Evangelists
Definition expert - noun - Unknown drip under pressure