Forum Discussion

shenyusun's avatar
shenyusun
Contributor
8 years ago

TestComplete Jenkins Plugin - GUI test, TestComplete did not launch it.

Hello Community,   I tired to integrate TestComplete project with Jenkins, but somehow TestComplete won't launch when Jenkins started to build. I was thinking maybe because "Silent' mode was passe...
  • shenyusun's avatar
    shenyusun
    8 years ago

    Support resolved the issue.

     

    The Jenkins Service needs to run by Local account.

shenyusun's avatar
shenyusun
Contributor

Hi Marsha,

 

Thank you for your help.

 

Yes, it worked if I typed the command manually. TestComplete launched, and then start doing UI tests.

I guess /SilentMode wasn't the issue.

 

shenyusun's avatar
shenyusun
Contributor
8 years ago

Somehow when Jenkins passed that to slave, TestComplete won't launch, but I can see TestComplete process stated, but usage didn't move that much.

  • Marsha_R's avatar
    Marsha_R
    Moderator
    8 years ago

    I see the Warning in the Jenkins log but I don't know what to do about that.

    [WARNING] The node is connected via Java Web Start (JNLP). In this mode, the "Run interactive user session" property of the TestComplete Test step is ignored. TestComplete (or TestExecute) will work in the current user session.

     The Run interactive user session is checked in your Settings but this disables it.

     

     

     

    Have you been through these steps and checked everything?

    https://support.smartbear.com/testcomplete/docs/working-with/integration/jenkins/running-tests.html

    • shenyusun's avatar
      shenyusun
      Contributor
      8 years ago

      yes, I checked it, and it looks good to me.

      Please see the screenshot below:

       

      I also get project file from SVN. That part should be fine because TestComplete launched without issue when I manually paste the command to cmd.

      But it would not launch when jenkins does it.

       

      I researched the warning, and then apparently that warning is normal.

      • shankar_r's avatar
        shankar_r
        Community Hero
        8 years ago

        Few you can try to identify the issue,

         

        • Have you verified this Build is triggering in the slave machine which you configured and manually tried? If not use below option to do it.
        • Try triggering the build when you have your slave opened by yourself
        • Try triggering the build after the disconnecting the slave
        • Try with Entire suite option

        I guess you will find some issues with above tries.