Forum Discussion

Anonymous's avatar
Anonymous
12 years ago

Jenkins integration - request for input

Dear testers it is well known that Jenkins is used widely to automate builds and some test activities, even though it is not explicitly designed to support test automation execution. People write t...
Colin_McCrae's avatar
Colin_McCrae
Community Hero
11 years ago
"My rant is related to the fact that I tried (and utterly failed) to integrate TC into TeamCity months ago"



Funnily enough, we have a TestComplete project run as part of the nightly build process in TeamCity.



But I suspect my approach is different to yours.



All my logging and reporting is done via script extensions which essentially form a data driven testing framework. This is all driven by user populated excel datasheets. A central script unit acts as the driver for all this. So the script extensions and driver unit form the shell of our automation projects that can easily be used on any new project.



So TeamCity builds the AUT. It then also installs it. Next step is to pull down the repo containing the TestComplete project and run that using TestExecute on a dedicated VM.



The project outputs an HTML file on completion with headline results and a couple of file links. From those file links you can drill down into greater levels of detail for the entire test run. TeamCity interprets both the return code from TestExecute and a couple of elements of the HTML file to indicate overall success or failure.



We find it works really well.



A couple of clever uses of global variable and dummy folders to indicate whether the project is being run in local (development) space or network (build) space as the behaviour varies slightly between the two and it's all portable and easy to use.
  • TanyaYatskovska's avatar
    TanyaYatskovska
    Icon for Alumni rankAlumni
    10 years ago

    Hi Guys,

     

    Thanks for sharing your thougths!

    We have recently released the new TestComplete 10.6 version, which comes with a new plug-in for Jenkins.

    Now, launching TestComplete and executing the needed test project can be done directly from Jenkins builds. Also, once tests are executed, the results get automatically updated to Jenkins.

     

    Online Documentation:

    Integration With Jenkins

     

    What do you think about this? Please share your ideas/suggestions.

    • matthieu_gironn's avatar
      matthieu_gironn
      Occasional Contributor
      10 years ago

      Hi,

       

      I've tried this yesterday and here are my comments.

      First this is a really good start for a first version of the plugin. The ability to run testexecute in another account is great.

      But I would add the folowing features:

      1. ability to select if a MHT file should be generated along with the htmlx and tcLogx reports. It is because we use the MHT file to share result with our customer.
      2. have a testcomplete graph or reports on the main job page that will display the history of tests results with a direct link to the corresponding logs. I'm thinking of something similar to the MSTest plugin http://wiki.jenkins-ci.org/display/JENKINS/MSTest+Plugin.
      3. display in the job output the progress of the tests with their results. Our tests are taking around 1, it would be nice to have in the output log of the running job. Not all the information would be necessary in the output log just the level of the log tree that you have in the tcLogX.

      Again this is a really good first version.

       

      Best regards,

       

      Matthieu Gironnet

      Persistent Systems