Script extensions are a very useful feature of TestComplete, allowing end users to create their own custom objects, checkpoints, keyword operations, etc., for use in their automation projects. We use script extensions in building out large sections of our automation framework, encapsulating functions like ADO SQL queries so that the code is accessible across all projects without needing to include files in every project.
At this time, when running test automation using the Environment Manager interface to CBT, these custom script extensions are not bundled into the project when it is sent to the virtual environment of CBT, meaning that any tests we construct which may use parts of our extensions will be unable to run on CBT.
I would like to see Script Extension support included in the interface to CBT. Perhaps look at the script extension directories of the TestComplete/TestExecute launch on the local machine, package up any TCX files found in those directories, copy them up to the CBT environment into the TestExecute instance there prior to launching the tests. This would make using the Environment Manager a more robust solution for testing in multiple browser environments by allowing more customization of code frameworks.
