Command line arguments in Jenkins plugin
We have just replaced our old home-grown Jenkins integration with the new 'official' SmartBear Jenkins-TestComplete integration. I find it very easy to work with and it has made our Jenkins integration more 'flashy' and easy to work with for people who are not working with the test system on a daily basis. One feature of our old setup was not possible to reproduce in the new. We sometimes need to run the test on branches of the code (other than the master branch). In our SUT this can be specified in the URL and in the old integration we called TC/TE with a command line argument to specify the branch (if different from master). Unfortunately the new Jenkins integration does not allow for arguments. Adding a field in the UI where you can specify a command line parameter to TestComplete/TestExecute would be nice. This field of course has to allow for variables, so you can pass the information round. This problem can of course be solved in other ways (e.g. dumping the information in a file or environment variable on the slave in Jenkins and read it in TC/TE), but we find our current implementation the most satisfactory. If someone has suggestions on how to implement an alternative, we will be glad to hear them. Yours, Søren Harder, QA engineer, Zmags
TestComplete Jenkins Enhancement
In the current version of the Jenkins plugin for TestComplete there are fields for user and password if running test as an interactive user session. Today these are freeform. I would like to make the recommendation that the plugin use the built in Jenkins credentials manager to select the user to run as from. In today's world with the need for increased security, we are required to have passwords rotate regularly. If we have hundreds of test jobs built out in Jenkins, we would have to modify each and every one of these each time passwords rotate. If the credentials manager is used, you can go to one location, and update the password for the account and not have to worry about modifying each individual job. Thoughts? Anyone else have this issue? Have you found other ways to address?
Jenkins TestComplete jobs should clean up processes
Usually a Jenkins build job injects cookies environment variables to processes it starts ("JENKINS_SERVER_COOKIE" and "HUDSON_SERVER_COOKIE"). Which are inherited into all child processes. And after job is finished, those processes are killed if still are left running. This does not work with TestComplete tests. My guess is, that this is because the TestComplete windows service is already running when job starts. Somehow TestComplete/TestExecute and all processes which are started by the scripts (e.g.via Win32API.WinExec) needs these cookie injected. I hope the Jenkins plugin API provides the means to retrieve the current cookie value.in Jenkins Plugin, mark tests as skipped
I would like to have the ability to mark tests as "skipped" (yellow in result graph) in JUnit . My assumption was, that tests resulting in log level "warning" are marked as such, but these are marked as "passed". An option to mark "warning" test results (MHT) as "skipped" (in JUnit-like test result) would be sufficient.