http://www.perlmonks.org?node_id=302400


in reply to Pros/cons of testing on remote systems?

Well what are you testing for?

The correct testing framework will depend on what the behaviour of the remote system is supposed to be. For instance:

A little more detail would help a great deal.

Also, applications like NetSaint may well already do a great deal of what you want to test.

Replies are listed 'Best First'.
Re: Re: Pros/cons of testing on remote systems?
by TASdvlper (Monk) on Oct 27, 2003 at 15:19 UTC
    ooops. didn't mean to add urls. ahhh ... Sorry for the lack of information. Basically, the remote system will most likely run scripts that we have generated, 3rd party scripts, unit tests (for developers), etc, really no limits. Basically, the master server will have what we call a "agenda" to run on a remote system (which is basically just a list of scripts to call - some in serial, some in parallel) and the master server will for a child for each unique call to a remote system. To break it down more: The master server may want to do this (very simple example). Agenda has 1 elemen. run: "perl /test/dvlp/mytestscript.pl <input 1> <input 2>" on remote system: 111.22.33.44 and get back the return code and any output (if available). I'm looking now if we can get back return codes from using the Telnet module ... no luck yet.