Forum Discussion

mcernello's avatar
mcernello
Occasional Visitor
8 years ago

Execute multiple projects of a suite in Jenkins

Hi, i am running a suite of tests complete using testComplete support plugin, in Jenkins.

What i need to do, or the ideal thing,  would be creating different jobs for the different projects that i have in my project suite. In a job i would run some projects, in another job another ones. What i mean to do is, instead of checking and unchecking projects that i need to run in my project suite, create those jobs that would do the same, run the projects that i need.

 

The problem is that the suite is really big in size, and currently i could not find another solution not being copying the whole suite to the folder of the different jobs, checking within the project suite only the projects that i need

 

I tried setting up different test complete steps or tests in the jenkins' job configuration, and in each step run a different project, but for each step, TestComplete opens and closes, instead of reamining open and run each step or project. That is very slow and makes my tests fail.

 

Is there a way to do such a thing? if i am not being clear, please let me know

Regards

4 Replies

  • m_essaid's avatar
    m_essaid
    Valued Contributor
    8 years ago

    Hi,

    I create Project Suites in which I add already existing projets "as existing items".

    By doing this, I prepare my checked items as I want them to be.

    Between this I need to make copies and "publish" all the projects somewhere. It gives me the ability to work on my genuine project, and let it unfinished after the end of the day : indeed, items are checked in the published projects.

  • shankar_r's avatar
    shankar_r
    Community Hero
    8 years ago

    Hi,

     

    I don't think there is a easy way to achieve your scenario since jenkins TestComplete Test will always launch new instance of TestComplete/TestExecute.

     

    As tristaanogre said if you remove /exit it will exit, unfortunately jenkins is not provided a option to edit the default command line parameters.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    There is a command line parameter for TestComplete of "Exit"... if you leave that out and add only the "run" command line, this will keep TestComplete/TestExecute running.

  • cunderw's avatar
    cunderw
    Community Hero
    8 years ago

    Currently there is no way to do this. This is because Test Complete is being launched under the Jenkins Job process, a new job will be a new process so there is no way to persist Test Complete between jobs.

     

    However, a couple points I would like to make, Test Execute would be a better fit for this scenario as it does not need to launch the full IDE, just the execution portion which is much much faster. 

     

    Another thing, if your tests are failing, I highly doubt it has anything to do with the time it takes to open / close Test Complete. That is outside the scope of your tests running. If your tests are failing there is most likely some other reason which needs to be investigated. 

     

    One solution would be to only copy over your project files and not the entire suite so that when each project is opened it's not opening the entire suite of however many projects all at once. Project suites are nice for development, but do not really provide much benefit in terms of running tests, especially since the more individual projects you add to it, the slower it will be to open and the more resources it will consume.