Forum Discussion

shankar_r's avatar
shankar_r
Community Hero
7 years ago

Installing and Loading Script Extensions

Hello,   I have created Script Extension for HTML reports and I am able to install and load the Script Extension using below options mentioned in the Smartbear help. https://support.smartbear.c...
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    1) TCX extension files are checked into source control so that they are in a standardized drive/folder hierarchy that will be common on all workstations

    2) Every machine configured to run tests, in either TestComplete or TestExecute, point Tools | Options | Engines | Script Extensions to that directory.

    3) When a new "pull" of latest source is done, the TCX is refreshed in the directory with the latest version

     

    This ensures distribution of the latest version of the script extension to all machines.  Note that step 3 needs to be done with the TestComplete/TestExecute application NOT running.  So, what we have is, for our over night runs, a batch file that pulls the latest source code done on a nightly basis a few minutes before the scheduled test run executes.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

1) TCX extension files are checked into source control so that they are in a standardized drive/folder hierarchy that will be common on all workstations

2) Every machine configured to run tests, in either TestComplete or TestExecute, point Tools | Options | Engines | Script Extensions to that directory.

3) When a new "pull" of latest source is done, the TCX is refreshed in the directory with the latest version

 

This ensures distribution of the latest version of the script extension to all machines.  Note that step 3 needs to be done with the TestComplete/TestExecute application NOT running.  So, what we have is, for our over night runs, a batch file that pulls the latest source code done on a nightly basis a few minutes before the scheduled test run executes.

  • shankar_r's avatar
    shankar_r
    Community Hero
    7 years ago

    2) Every machine configured to run tests, in either TestComplete or TestExecute, point Tools | Options | Engines | Script Extensions to that directory.

     

    So, This is needs to be done manually in all machines which are running the TestExecute/TestComplete only for first time.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago
      shankar_r wrote:

      2) Every machine configured to run tests, in either TestComplete or TestExecute, point Tools | Options | Engines | Script Extensions to that directory.

       

      So, This is needs to be done manually in all machines which are running the TestExecute/TestComplete only for first time.

      Correct.  It's a one time configuration.  You don't need to do it every time you edit an extension.

      • shankar_r's avatar
        shankar_r
        Community Hero
        7 years ago

        Got it, I was wondering whether we can do this as like pulg-ins. 

         

        However, i got what are said. Will implement in our env also.