Quantcast
Channel: New board topics in SmartBear Community
Viewing all articles
Browse latest Browse all 21061

cm does not recognize command when launched through TestComplete script

$
0
0

 

When I manually launch cmd and type telnet and press enter, I get the message "Welcome to Microsoft Telnet Client", as I would expect.

 

I wrote a vbscript routine in TestComplete to do the same, but when I run it I get "'telnet' is not recognized as an internal or external command, operable program or batch file." in the cmd window.

 

Here is a sample:

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

sub test
dim wscriptObj

set wscriptObj = createobject("WScript.Shell")

Call wscriptObj.run("cmd.exe")
Call delay(1000)
Call wscriptObj.SendKeys("telnet{Enter}")
end sub

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

 

I also tried using 'set wscriptObj = sys.oleobject("WScript.Shell")', but still got the same result.

 

I even tried making cmd a testedapp, ran the testedapp and used the keys method instead of sendkeys to type, but still got the same result.

 

So I went into notepad with the original code from above and created a vbs file containing the below:

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

dim wscriptObj
set wscriptObj = createobject("WScript.Shell")
Call wscriptObj.run("cmd.exe")
call wscript.sleep(1000)
Call wscriptObj.SendKeys("telnet{Enter}")

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

 

And when I run that, separate from testcomplete, that works successfully.

 

As far as I can tell, based on the caption of all the cmd windows, I am always launching the system32 cmd (manually, through vbs, and through testcomplete).

 

Is there something I am missing?


Viewing all articles
Browse latest Browse all 21061

Trending Articles