background image
<< Multi-Application - invokes SetMultiBaseStates and DisconnectAll | Multi-Application - template.t explained >>
Multi-Application - Recording window declarations for remote machines
<< Multi-Application - invokes SetMultiBaseStates and DisconnectAll | Multi-Application - template.t explained >>
386
User's Guide
22 M
ULTI
-A
PPLICATION
T
ESTING
Recording window declarations for remote machines
Recording window declarations for remote machines
Recording window declarations on a client machine that is not the host
machine requires that you operate both SilkTest on the host machine and the
application on its machine at the same time. You record window declarations
and application states in much the same way for a remote machine as for an
application running in the SilkTest host machine. The primary difference is
that you start the recording operation by selecting Test Frame in SilkTest on
the host system and you do the actual recording of application operations on
the remote system.
If you have two or more applications being tested in parallel, you need to
have two or more sets of window declarations. You must have window
declarations (and application states, if needed) for each different application.
When recording window declarations and application states on a remote
machine, you will find it convenient to have the machine physically near to
your host system.
Code for template.t
This fragment of an example testcase shows the required code with which
you start a multi-application testcase. It connects SilkTest to all the machines
being tested and brings each to its first screen. This is just a template; you
must tailor your code to fit your actual needs. The next section explains the
significance of each of these lines of code.
multitestcase MyTest (STRING sMach1, STRING sMach2)
SetUpMachine (sMach1, MyFirstApp, "MyFirstAppState")
SetUpMachine (sMach2, MySecondApp, "MySecondAppState")
SetMultiAppStates ()
spawn
SetMachine (sMach1)
// Here is placed code that drives test operations
spawn
SetMachine (sMach2)
// Here is placed code that drives test operations
rendezvous
// . . .