I have created a couple of script extensions successfully, but I am now working on another one that is giving me some troubles.Whenever I call one of it's methods from my scripts, I get a "Class doesn't support Automation: 'Namespace.Name.method'" assertion.I am running out of ideas on what could be the cause of this.Could you please give me a hand?I will attach the extension here.

Hi Everybody, I have some news for you - our R&D team confirmed that this is a problem in TestComplete, and it's going to be fixed in one of future product updates. Thanks to Christian who discovered the issue and to all of you for your great assistance in this question!

Hi Christian,plinkCommand variable in the executeCommand() function is of string type, thus instead of 'Clean sensitive data Set plinkCommand = Nothingyou should write 'Clean sensitive data plinkCommand = ""P.S. It is possible to copy unpacked components of the script extension (description, script files, etc.) into subfolder below the ScriptExtensions folder and debug them as regular script in TestComplete.

It might be related to the first item in the list here.http://support.smartbear.com/viewarticle/27101/"Writing Script Extensions - Specifics"

Hi Christian, Do you get this error when running one of the methods directly from TestComplete's Code Editor?

Here is an example of a script that gives the error. This is in another unit, I RightClick on it and select "Run Current Routine"----------------------------------- Sub Test_executeCommand command = "ls /dr01/files/db*.sqldump" Set linuxLoginData = InstanceOf_LinuxLoginData linuxLoginData.user = "testuser" linuxLoginData.host = "host20" linuxLoginData.password = "testpassword" data = Linux.Plink.executeCommand(command, linuxLoginData) (<--- This line crashes) log.message(data) End Sub ----------------------------------- This is the error from the Additional Info in the logs: Class doesn't support Automation: 'Linux.Plink.executeCommand' Error location: Unit: "PSuite\Proj\Script\Unit13" Line: 8 Column: 3. -----------------------------------

Problem with Script Extension: Class doesn't support Automation

20 Replies

TanyaYatskovska
SmartBear Alumni (Retired)
11 years ago

Hi Everybody,

I have some news for you - our R&D team confirmed that this is a problem in TestComplete, and it's going to be fixed in one of future product updates.

Thanks to Christian who discovered the issue and to all of you for your great assistance in this question!
AlexKaras
Champion Level 3
12 years ago
Hi Christian,

plinkCommand variable in the executeCommand() function is of string type, thus instead of

'Clean sensitive data

Set plinkCommand = Nothing

you should write

'Clean sensitive data

plinkCommand = ""

P.S. It is possible to copy unpacked components of the script extension (description, script files, etc.) into subfolder below the ScriptExtensions folder and debug them as regular script in TestComplete.
rminnich
Contributor
12 years ago
It might be related to the first item in the list here.

http://support.smartbear.com/viewarticle/27101/

"Writing Script Extensions - Specifics"
TanyaYatskovska
SmartBear Alumni (Retired)
12 years ago

Hi Christian,

Do you get this error when running one of the methods directly from TestComplete's Code Editor?
ekiza23
Contributor
12 years ago
Here is an example of a script that gives the error. This is in another unit, I RightClick on it and select "Run Current Routine"

-----------------------------------

Sub Test_executeCommand

command = "ls /dr01/files/db*.sqldump"

Set linuxLoginData = InstanceOf_LinuxLoginData

linuxLoginData.user = "testuser"

linuxLoginData.host = "host20"

linuxLoginData.password = "testpassword"

data = Linux.Plink.executeCommand(command, linuxLoginData) (<--- This line crashes)

log.message(data)

End Sub

-----------------------------------

This is the error from the Additional Info in the logs:

Class doesn't support Automation: 'Linux.Plink.executeCommand'

Error location:

Unit: "PSuite\Proj\Script\Unit13"

Line: 8 Column: 3.

-----------------------------------
ekiza23
Contributor
12 years ago
Any hint on what I could look into next to try and fix this?
rgratis
Frequent Contributor
12 years ago
A few things I might try:

include the class definitions (Linux_Classes) directly into the plink.vbs file to see if there is an issue accessing the argument class

Create empty Init/Term routines for the Plink runtime object and add to the Script element in Description.xml
ekiza23
Contributor
12 years ago
Thanks for the recomendation, Alexei, I will try to be more consistent with these things.

However, this has not fixed te problem.

I read earlier about debugging script extensions, but couldn't make it work. I will try again, but I have used these commands as regular project scripts and they all worked fine.

It is when I tried to pack them in a Script Extension that I started seeing this error, so I suspected that it was either something wrong with the Description file or something more related to the ScriptExtensions functionality that I was not aware of ...
ekiza23
Contributor
12 years ago
I tried the debugging,

I copied and unpacked the components of the script extension into subfolder below the ScriptExtensions (I moved the version of the extension in this folder from 1.3 to 1.4 to make sure it was being correctly loaded), I "uninstalled" the extension and then I reloaded it, and it was effectively 1.4.

I tried to run the script and the same error was reported... I am not capable of finding any useful information to debug it.
ekiza23
Contributor
12 years ago
Creating empty init/term routines did not work either.