Forum Discussion
r_simms
12 years agoNew Contributor
Hi everyone.
Thanks for the replies.
Unfortunately neither solutions worked for me. My machine uses Office 2013 so I could not verify if that plug in worked or not, and the command line snippet still has the same issue of opening and closing without being able to see a result.
With the command line snippet, TestComplete will always say it fails regardless. Even if I use a ">> output.txt" to pipe the result to a text file to see an actual result, nothing gets created. I'm assuming this means something is going wrong somewhere.
Is there a way for the command prompt to not close immediately? Like a "Pause"?
Many thanks for the help so far.
Thanks for the replies.
Unfortunately neither solutions worked for me. My machine uses Office 2013 so I could not verify if that plug in worked or not, and the command line snippet still has the same issue of opening and closing without being able to see a result.
With the command line snippet, TestComplete will always say it fails regardless. Even if I use a ">> output.txt" to pipe the result to a text file to see an actual result, nothing gets created. I'm assuming this means something is going wrong somewhere.
Is there a way for the command prompt to not close immediately? Like a "Pause"?
Many thanks for the help so far.