Forum Discussion
You need Test Complete or Test Execute installed on the machine that you want to run the tests on. The plugin merely reports test results back to Jenkins, thats it.
You do not have to have Jenkins installed on the same machine but you can do this if you want. Normal practice would be to have it installed on a server somewhere with seperare testing hosts. If you have the Jenkins JNLP agent (https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds) installed on the machine that you are running tests on and it can communicate with the machine running Jenkins then you are good to go.
Additionally if you dont like the plugin you dont need to use it. You can configure a project in Jenkins and have it call Test Execute or Test Complete from the command line (http://support.smartbear.com/viewarticle/54705/) and then access the log files in the project history in Jenkins. I had Jenkins configured like this for a while before we went back to QA Complete :-( and it works great.
In this case:
"You do not have to have Jenkins installed on the same machine but you can do this if you want. Normal practice would be to have it installed on a server somewhere with seperare testing hosts. If you have the Jenkins JNLP agent (https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds) installed on the machine that you are running tests on and it can communicate with the machine running Jenkins then you are good to go."
Can I do that using just one license?
- chrisb10 years agoRegular ContributorOK, I'm assuming you have just one test complete license. In which case you can't be developing and running tests at the same time. So yes you can start your tests with Jenkins with one license either with Jenkins on the same machine as test complete or on a separate machine.
- sha10 years agoContributor
I may be stating the obvious here, but you can have TestComplete installed on as many machines as you want. But when you actually start the program, it will communicate with the license server and block the program, if you do not have enough licenses. So you can develop on one machine and run tests at another machine; but not at the same time. If your automated tests starts when you are working on another computer, it will just fail with a helpful error message.