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?
> 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).
So I am starting TestComplete. I feel TestExecute is internally opening TestComplete. Because I can see the pop up( Please refer Attachment). Any other idea why this pop up is coming?
When i run this command TestExecute.exe "C:\Work\SmartBear\TestExecute\Projects\My\MySuite.pjs" /r /p:MyProj (with other self healing, export log and do not Show log parameter). I see the attached pop up coming up.
> Any real problem with the /Silent parameter?
Yes it can disable few error pops or warning which is important to look at. I don't want to miss such pop ups. And it is not feasible to look at silent.log file every time
Hi,
> So I am starting TestComplete. I feel TestExecute is internally opening TestComplete.
It looks like we are talking about different things...
If you start TestComplete, it is opened on your desktop and you will not be able to start TestExecute while TestComplete is running. Likewise for TestExecute - if you start TestExecute, its icon is displayed in the Windows Tray (with context menu accessible via the right click) and you will not be able to start TestComplete while TestExecute is running.
The informational window that is displayed while test suite is been opened is a regular informational window displayed by both TestComplete and TestExecute and is not an indication that one of them spawns another. Use Windows Task Manager to check this.
> it can disable few error pops or warning which is important to look at.
No again. As per documentation, /Silent parameter just suppresses prompts from TestComplete/TestExecute and applies default actions. All warnings and error messages from the tested application should be either gracefully processed by test code or logged to the test log. While you may watch how test code executes while creating/debugging test code, it is not a good practice to rely on visual watching and/or visual messages from TestComplete/TestExecute in the production tests runtime.
