background image
<< Client/Server Testing - Incremental functional test design | Client/Server Testing - Testing clients plus server serially >>
Client/Server Testing - Running tests on one remote target
<< Client/Server Testing - Incremental functional test design | Client/Server Testing - Testing clients plus server serially >>
374
User's Guide
21 I
MPLEMENTING
C
LIENT
/S
ERVER
T
ESTING
Running tests on one remote target
The rest of this chapter describes and gives examples of the techniques you
use to direct test operations to one or more remote target applications and to
control whether those tests run serially or concurrently.
Running tests on one remote target
Ways to specify a
single remote target
There are three ways in SilkTest to specify that you want a script, suite, or
testplan to run on a remote target instead of the host:
Enter the target Agent's name in the host's Runtime Options dialog. You
also need to select a network protocol in the dialog.
In a suite, specify the target Agent's name by enclosing it within brackets
before the script or suite name:
[Ohio]myscript.t
You can select "(none)" in the host's Runtime Options dialog and then
specify the target Agent's name in a call to the Connect function in your
script. For example, to connect to a machine named Ontario:
testcase MyTestcase ()
Connect ("Ontario")
// Call first testcase
DoTest1 ()
// Call second testcase
DoTest2 ()
Disconnect ("Ontario")
When you are only driving one remote target, there is no need to specify the
current machine; all testcase code will automatically be directed to the only
connected machine.
When you use the multi-application support functions, you will not have to
make explicit calls to Connect; the support functions will issue these calls for
you.
Running tests serially on multiple targets
To run your scripts or suites serially on multiple target machines, specify the
target Agent's name within the suite file. For example, this code runs a suite
of three scripts serially on two target machines named Ohio and Montana:
[Ohio] script1.t
[Ohio] script2.t
[Ohio] script3.t
[Montana] script1.t