Andreja,
I do not run this test inside the project for web testing but inside the project for testing Windows apllications |
The project does not matter, that is, it does not affect the way TestComplete simulates user actions.
maybe I should include some another project item into my project because of this API calls in the background... |
As far as I know, that does not matter either. Many applications process things in the background, and that does not cause problems.
At the moment, I can see three possible causes of the problem: TestComplete hangs, your script code hangs (or goes into an infinite loop), or your application hangs.
To check whether it is TestComplete that hangs, switch to it during the test run (when you think the test hangs) and click editors, menu items or select nodes in the Project Explorer. Most of the actions will be disabled (that is, menu items will be disabled, or you will not be able to change anything in the editors), but the clicks should work: you should be able to see menu items, changes in the cursor position in the script editor, changes of selection in the Project Explorer and so on. If TestComplete does not respond to clicks, it is hanging.
To determine whether your test is hanging, I suggest posting the d variable to the test log. This way you will see if it exceeds 50. That means the script goes into an infinite loop and you need to change conditions in your script code.
Unfortunately, it's difficult for me to say what goes wrong in your case. I suggest that you contact the SmartBear Support Team. Please send them your test project along with test log data (as I wrote you earlier). Also, please tell them a bit more about the problem: if it is TestComplete, your script or your application that hangs.