I am a test engineer that is currently designing a automation system. Basically, the thought is the master server will run tests on multiple remote systems and gather return codes, messages, etc. So, there are 3 solutions I am looking at (but not limited too): rsh, telnet/expect (using the Telnet/Expect modules) or client/server (usiing IO::Socket) app.
I was wondering if anybody had experience with the above and has suggestions/recommendations on what is the best approach ? I just started my research and they all seems to have some pros/cons.
One gotcha I need to keep in mind, is that our remote systems, that run tests, could be a variety of different OS's (Windows, Solaris, NetBSD just to name some).
Any feedback on this would be greatly appreciated. Thx
update (broquaint): title change (was Testing on remote systems: what is the most robust (logical approach): rsh, telnet/expect or client/server app (or others ?))
In reply to Pros/cons of testing on remote systems? by TASdvlper
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |