1. For /SilentMode: If this argument is specified, TestComplete works in Silent mode, that is, it neither displays dialogs, nor informs you about errors or warnings. The dialogs and messages to be displayed are handled as if you pressed the default button in them. "- I can't tell you exactly what gets suppressed or not. I think it's a fair assumption to say that most everything would be (including those error/warning dialogues). I've also seen that using the /exit argument closes the instance down immediately after the test runs as well.
2. I'd then suggest using /ExportSummary or /ExportLog arguments to achieve this end goal - this way, even in silentmode, you can take a look at your test results whenever you want by finding the files within that specified directory.
3/4. I think the options above address the needs that we dont really need to explore this option.
Thanks Kim for your reply.
I am already using /ExportLog parameter with testExcute and its exporting my log.
But the issue is not with TestExecute, It with testComplete. If you run a test case in TC through TE, log is generated in TC also. Because of which I am getting confirm dialog to save any changes to our project. My main goal is not to get the confirm dialog or it should by default select yes and save the changes.
I do want to explore 3rd and 4th option if 1 & 2 doesn't work 🙂
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?
