Forum Discussion

liquidphantom's avatar
liquidphantom
Occasional Contributor
7 years ago
Solved

Forcing TestExecute updates on remote VM

I currently have TestExecute working with our CI using TeamCity, I'm getting rather frustrated with TestExecute updates for Firefox however which seem to be quite regular and hold the build step up as it's waiting for input on the remote machine, obviously, because the Test is performed out of office is hourse there is no way to know until I come into to see that the build step has been held up for ages or just timed out.

 

Short of disabling updates altogether is there anyway to force the updates?

 

Thanks

  • I guess /SilentMode command line argument can handle your scenario. Have you added this command line into your TestExecute command line parameters in TeamCity.

     


    From Smartbear docuemnt

     

    /SilentMode - If this argument is specified, TestExecute works in silent mode, that is, it neither displays dialogs, nor informs you about errors or warnings. The dialogs and messages to be displayed are handled as if you pressed the default button in them. Information about these dialogs and messages is saved to the following file:

    <Users>\<User_Name>\AppData\Roaming\SmartBear\TestExecute\12.0\Silent.log

    The file should not be read-only or locked by another application.

    The errors that occur during the test run are posted to the test log.


     

    Helpful links : https://support.smartbear.com/testcomplete/docs/app-testing/web/general/preparing-browsers/firefox.html

2 Replies

  • shankar_r's avatar
    shankar_r
    Community Hero

    I guess /SilentMode command line argument can handle your scenario. Have you added this command line into your TestExecute command line parameters in TeamCity.

     


    From Smartbear docuemnt

     

    /SilentMode - If this argument is specified, TestExecute works in silent mode, that is, it neither displays dialogs, nor informs you about errors or warnings. The dialogs and messages to be displayed are handled as if you pressed the default button in them. Information about these dialogs and messages is saved to the following file:

    <Users>\<User_Name>\AppData\Roaming\SmartBear\TestExecute\12.0\Silent.log

    The file should not be read-only or locked by another application.

    The errors that occur during the test run are posted to the test log.


     

    Helpful links : https://support.smartbear.com/testcomplete/docs/app-testing/web/general/preparing-browsers/firefox.html

    • liquidphantom's avatar
      liquidphantom
      Occasional Contributor

      Thanks! I had that in initially but then took it out to test a setup and forgot about it.

       

      I'll put it back in and hopefully that will sort it.