Unable to open TestComplete via batch file
Hi All, I am opening test complete via Batch file. During opening some times i am getting following error. How to handle this error? Could you please add your comments and let me ...
Forum Discussion
Hi,
Please provide the content of your batch file and show problem details (in TC dialog).
Yeah.
As baxatob says, you need to provide more info.
At the moment, your question effectively reads "Why doesn't TestComplete work?". I suspect you can see why no-one is going to give you a sensible answer! :smileywink:
(I hope you give your devs more info than this when you raise bugs!!!)
Adding more details here
I am opening Test Complete via cmd line.
The following command is using while opening the TC.
start /wait "" "C:\Program Files (x86)\SmartBear\TestComplete 11\Bin\testcomplete.exe" /DisableDump "\\testcomplete 11\project.mds" /r /silentmode /ns /e /el:%expLocation% /p:"Project"
In some scenarios only, I am facing the above error. How to handle/fix this error.
Is there anyway to handle weird exceptions while opening TC via cmd line through TC.
Let me know if you require more details.
Regards. BommaReddy
Still need more info ....
In some scenarios only, I am facing the above error.
Which scenarios?
When exactly does it crash? On starting TC? Part way though a test? (And is it certain tests only?) When it's shutting down TC?
What are the crash details? You have still cut off the error details panel of the crash window.
You should be able to capture some crash info from your batch script.
Helpful guide on the basics of batch scripting: http://steve-jansen.github.io/guides/windows-batch-scripting/part-3-return-codes.html
My batch script for running Test Execute checks a whole bunch of things to make sure it runs properly. Kills any existing instance of TE. Runs the test via TE command line. Checks the TE return code. Checks output written elsewhere on the network and then the batch file itself generates a return code based on all this info which feeds into our CI service. And all of these are wrapped in their own error handlers in case it can't find TE, or the project or whatever.
