Documentation for 3.15
Other versions: trunk  3.27  3.26  3.25  3.24  3.23  3.22  3.21  3.20  3.19  3.18  Older...

Running tests on a remote machine
(Without the aid of a grid engine)
Note : This functionality does not currently work on Windows. Most of the description below applies in principle but at the moment it generates a UNIX Bourne-shell script which is executed on the remote machine.
Basic set-up
On the Running/Basic tab in the static GUI, there is an entry "Run on machine". This can be used to divert tests to run on other machines on the network than the local one. This can also be done from the command line via the "-m" option. By default this assumes that the remote machine and the local machine are on a shared file system of some sort.
Sometimes your tests may only work correctly on particular machines, and in this case it's useful to set the default machine to one of these so that you don't have to remember to enter it each time. For this there is a config file setting "default_machine".
Tests will be submitted to the machine via "rsh", unless you override the config file setting "remote_shell_program", for example to "ssh" or "plink". TextTest makes every effort to provide default arguments to these programs that are sensible for batch testing: i.e. will fail rather than ask for passwords etc. To this end there is a dictionary config file setting "remote_program_options", which sets such values for typical remote shell programs. You shouldn't need to change this under normal circumstances unless you use a remote shell program we haven't used. Look at the table of config file values to see which arguments will be provided by default.
It's worth noting that rather more advanced, and parallel, usage can be made of remote machines if a grid engine program is also installed. See the document on running tests in parallel. If you do have a grid engine installed and also provide the "Run on machine" setting (or "-m" on the command line), this will be automatically translated into a grid engine resource so that the test runs there by way of the grid engine.
Running on a different network
There is also support for running tests on systems even where the file system is not shared. This will of course be slower as the system under test and test data will need to be copied to the remote file system at the start, and the test result will need to be copied back again after the test. To enable it, set the config file entry "remote_copy_program" to some program that can copy files to remote systems, for example "scp", "rsync" or "pscp". Default arguments for these programs are also provided via the "remote_program_options" config file entry as above.

Last updated: 05 October 2012