Forum Discussion
From Smartbear. Not a good idea to trust PSEXEC to work:
"There is a number of known problems with psexec and we cannot guarantee that TestComplete / TestExecute will work correctly when launched by psexec - that's caused by some specifics of the third party tool's implementation. This means that you may observe problems with tested applications launched by psexec as well.
If you need to run TestComplete tests remotely, we recommend that you consider using the Network Suite feature instead (see the "Distributed Testing" (http://smartbear.com/viewarticle/80602/) help topic for more information)."
That said, I would still like a way where I don't have to use two licenses via NetworkSuite (master and slave) to run one test suite triggered from Bamboo.
The quest continues.
I'm assuming Bamboo doesn't allow you to open a WScript shell prompt or command prompt and just execute a command line? That seems to be the quickest work around. It's not a direct integration between Bamboo and TestExecute, but it will at least allow you to run the tests.
- maximojo9 years agoFrequent Contributor
tristaanogre the problem is I'm trying to execute tests on a remote VM, not the build server machine. This is the crux of the problem :)
Related Content
Recent Discussions
- 3 days ago
- 3 days ago
- 7 days ago