Forum Discussion
I agree with DWalsh . TestComplete does not have any settings or anything to automatically close the application under test. This is something that needs to be explicitly called within the test itself or as an event handler. If you can share your code or a screenshot of your KWT, we can perhaps help further.
Yes, this is my first test. And I am opening the app manually.
Line 9 opens the new window(say Window B) in the app and closes the first window(window A). (This is working fine)
Line 17 should close the Window B and return back to Window A, but it closes Window B and does not go back to Window A.
In Task Manager, I can see the process running for the app but there is no window present in UI.
Please let me know if any more info is required and thanks in advance for help.
- tristaanogre5 years agoEsteemed Contributor
If you're expecting Window A to be back with the application present in Task Manager, that doesn't sound like a problem with the automation but a bug in the application under test.
I'm assuming that if you try it manually, it also doesn't work right? I would say, at this point, generate a bug report back to your developers and see what they have to say. By definition, if you're expecting a behavior and that behavior doesn't happen, then it's a bug.- pankajjain20505 years agoContributor
It works fine manually. Also works fine with Winium driver automation.
Somehow doesn't work with Testcomplete :-(
- tristaanogre5 years agoEsteemed Contributor
Is code the result of a recording or did you manually create it? What happens if you record your steps and then replay?
Related Content
Recent Discussions
- 5 hours agojstaehlin
- 23 hours agoAivanitskiy