Ask a Question

Script Extensions are not defined when running Jobs

New Contributor

Script Extensions are not defined when running Jobs

I have created a few Script Extensions and they work on my computer. But when I try to run a Job then I get a reference error saying "<Script Extension name> is not defined". I have checked the slave computer and it does have the Script Extension files and the description.xml file, so why am I getting this error?

Esteemed Contributor

On the slave machine, if the tcx files are in a different folder than the default (<testcomplete installation folder>\Bin\Extensions\ScriptExtensions), you need to go into the options and point to the different folder.  In TestComplete, this is in Tools -> Options -> Engines -> Script Extensions.  In TestExecute, right click on the Sys try icon, select Options -> Engines -> Script Extensions

Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available

That worked! Thank you so much. I am using TestExecute; I also verified that the Script Extensions were there by right clicking the tray icon, and selecting Install Script Extensions.

Showing results for 
Search instead for 
Did you mean: