Close TestComplete before you run the automation in TestExecute. The confirmation you're getting is because TestExecute is updating project objects (tcLogs) that TestComplete has open so it wants to notify you that something needs to be updated.
Thank you .
That's a great idea.
But the issue is I am not launching TestComplete. I think on running test cases in TestComplete through TestExecute, TestExecute internally launches TestComplete in hidden mode. Because when test execution begins I can see notification, Project opening.
So is there any way that TestComplete doesn't launch by itself? Or can testcomplete process be killed before confirm dialog comes up?
Hi,
> TestExecute internally launches TestComplete in hidden mode.
No. TestExecute is a standalone run-time. TestComplete is the IDE which uses the same engine (code, but not TestExecute application) when executing the test. TestComplete and TestExecute can co-exist on the same box but only one of them can run at the given moment of time.
Hi,
So when i run test case in TC through Test Excute 14.4 following pop up comes up.
So internally is TestExecute is opening Testcomplete?
After the automation completes i get following confirm dialog
My main aim is not to get this pop up. As this is hindrance to smooth execution of 1000+ test case through automation. This pop requires manual intervention i.e someone to click on yes/no.
Any other way apart from /silentmode parameter to avoid this pop up?
Hi,
> when i run test case in TC through Test Excute 14.4
No. On the given box at the given moment of time test case can be run either via TestComplete or via TestExecute. Either TestComplete or TestExecute can be started, but not both. They are two separate applications and do not call each other during runtime (though definitely contain some identical functional blocks).
Any real problem with the /Silent parameter?
