Background: After executing test in Test Complete through Test Execute, Confirm dialog of Test Execute comes up to save the changes in mds file. So basically this confirm dialog comes up to save log file generated after execution of test
My requirement is not to get the confirm dialog after execution.
1 One way is running Test Excute in /SilentMode but what other pop ups will be disabled?(I am apprehensive about this option because i don't want to disable valid related error pop up)
2 Can anyone tell how to automatically save the log file so that confirmation message didn't come up.
3 Or How to Access TestExecute Objects in TestComplete so that through automation i can automatically click yes in confirm button?
4 Or any way to select default option yes in the confirm dialog?
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?
> 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.
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?
> 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
> 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.