Remote Tcl testing on Windows from Linux
Earl Greida
network testing, and client testing which runs under both Linux and Windows.
The automation environment run under Linux.
I have never had to deal with Windows, from a test automation perspective,
and am at a loss as to how to connect to a Windows PC from the Linux
automation environment, start a test script, and get the results. With
Linux you can simply use Expect, telnet to the Linux PC, and start the test.
Since Windows was kind enough to not include a telnet/ftp server just how
can a 3rd party access a remote Windows (2000, XP, Vista) PC, run a test,
and get the results?
Wojciech Kocjan
napisał(a):
> I have a new job that requires developing Tcl test programs for
> automating
> network testing, and client testing which runs under both Linux and
> Windows.
> The automation environment run under Linux.
Have you considered installing cygwin+sshd on Windows?
When I did similar testing environment, I installed cygwin+sshd,
integrated the key authorization and there wasn't any difference from a
Unix box.
--
WK
email (rot13): jbwpvrpuNGxbpwnaQBGbet
Cameron Laird
Wojciech Kocjan <wojci...@gazeta.pl> wrote:
.
.
.
>> I have a new job that requires developing Tcl test programs for
>> automating
>> network testing, and client testing which runs under both Linux and
>> Windows.
>> The automation environment run under Linux.
>
>Have you considered installing cygwin+sshd on Windows?
>
>When I did similar testing environment, I installed cygwin+sshd,
>integrated the key authorization and there wasn't any difference from a
>Unix box.
.
.
My first thought is to use the telnet service which is part
of modern Windows installations.
There are LOTS of variations depending on the details of
Earl's situation. There are sshd-s which don't require all
of cygwin, it's easy to install a Tcl "reactor" which simply
launches the tests of interests, and, with enough motivation,
I think there's a way to use Samba and Windows authentication
methods to launch what we regard as remote processes (I've
been procrastinating for years in search of an excuse to
pursue this one).
Earl Greida
Wojciech Kocjan wrote:
> Dnia 14-01-2007 o 01:32:35 Earl Greida
> <eGREGIO...@FREEyahoo.commit> napisał(a):
>
>> I have a new job that requires developing Tcl test programs for
>> automating
>> network testing, and client testing which runs under both Linux and
>> Windows.
>> The automation environment run under Linux.
>
> Have you considered installing cygwin+sshd on Windows?
>
No, because I did not know of it. Other than using Windows for
reading/writing email, Usenet and Internet surfing, etc. I have never had to
"work" on it, from an automated testing perspective. Before I just dealt
with testing network equipment, now I have to add testing a Windows client
program into the mix.
Earl Greida
Cameron Laird wrote:
> In article <op.tl40n...@ibm-81752006df5.ibm.com>,
> Wojciech Kocjan <wojci...@gazeta.pl> wrote:
> .
> .
> .
>>> I have a new job that requires developing Tcl test
>>> programs for automating network testing, and client
>>> testing which runs under both Linux and Windows.
>>> The automation environment run under Linux.
>>
>> Have you considered installing cygwin+sshd on Windows?
>>
>> When I did similar testing environment, I installed cygwin+sshd,
>> integrated the key authorization and there wasn't any difference
>> from a Unix box.
> .
> .
> .
> My first thought is to use the telnet service which is part
> of modern Windows installations.
>
I didn't know that Windows now included a telnet server. I know there is a
telnet client so you can telnet from a Windows box to Linux, but did not
know you could telnet from Linux to Windows. However, this reminded me that
I did use smbclient/expect in the past to connect to a windows box and get a
file from it. Maybe smbclient will also act like telnet/expect.
Melissa Schrumpf
> I didn't know that Windows now included a telnet server. I know there is a
> telnet client so you can telnet from a Windows box to Linux, but did not
> know you could telnet from Linux to Windows.
There is, but it is miserably insecure. IIRC, it has even more issues
than standard telnet. I forget the details, but for some reason I'm
thinking that it doesn't even require login authentication. I may be
wrong on that point.
But if your environment is secure enough (e.g. stand-alone LAN segment),
it's completely usable.
Remember, though, that with telnetd or sshd, you'll still need to log in
to the windows shell if any of your testing involves Tk.
--
MKS
Gerry Snyder
> ....
>
> I ... am at a loss as to how to connect to a Windows PC from the Linux
> automation environment, start a test script, and get the results.
One possibility, easy to set up and not mentioned so far, would be to
run a cgi-aware web server on the Windoze PC, accessed by any browser on
Linux.
DustMotePlus might be enough--check out http://wiki.tcl.tk/16867
HTH,
Gerry
Uwe Klein
would something using VNC help?
There are at least some hints about remote testing
on the web using VNC:
http://www.google.com/url?sa=t&ct=res&cd=6&url=http%3A%2F%2Fcivicspacelabs.org%2Fnode%2F13799&ei=hzWrRbutG4aYnQP_wMj7Dw&usg=__6X2G-IcahLi6O-i4T7m3nY_A8Xw=&sig2=RvgFXuWpL1ADde_9OCHPOQ
http://www.google.com/url?sa=t&ct=res&cd=7&url=http%3A%2F%2Fwww.vncrobot.com%2F&ei=hzWrRbutG4aYnQP_wMj7Dw&usg=__n0p-6ztbLuLw59PlboTWKnnQPIE=&sig2=gHKC5waCdBwvY1iY-cAMLg
found with:
http://www.google.com/search?q=vnc+client+remote+testing
uwe
ic...@netrover.com
Depending on what you need to do to "get results", you might look into
the SIMPL toolkit (http:/users.netrover.com/~ican/simpl). It has
Tcl/Tk hooks which can allow you run a Tcl/Tk Windows socket enabled
app and make it look like a SIMPL app to your Linux station.
For and example of this in practice see
(http://hometoys.com/htinews/apr06/articles/appliance/part2.htm)
bob