background image
<< Implementing Client/Server Testing | Client/Server Testing - Using 4Test's parallel processing features >>
Client/Server Testing - Evolving a testing strategy
<< Implementing Client/Server Testing | Client/Server Testing - Using 4Test's parallel processing features >>
364
User's Guide
21 I
MPLEMENTING
C
LIENT
/S
ERVER
T
ESTING
Evolving a testing strategy
Evolving a testing strategy
There are several reasons for moving your QA program from local to remote
testing:
You may have a stand-alone application that runs on many different
platforms and now you want to simultaneously drive testing on all the
platforms from one SilkTest host system.
You may have been testing a client/server application as a single local
application and now you want to drive multiple instances of the
application so as to apply a heavier load to the server.
You may want to upgrade your client/server testing so that your testcases
can automatically initialize the server and recover from server failures--
in addition to driving multiple application instances.
You may need to test applications that have different user interfaces and
that communicate as peers.
If you are already a SilkTest user, you will find that your testing program can
evolve in any of these directions while preserving large portions of your
existing tests. This chapter helps you to evolve your testing strategy by
showing the incremental steps you can take to move into remote testing.
Think of this chapter as a tutorial that introduces the details of multi-
application, remote testing in small pieces--while preparing you for the fully
developed testing strategy described in Chapter 22, "Multi-Application
Testing."
Note that while the testing techniques introduced in this chapter are all valid
and might find use in your testing programs, the complete power of SilkTest
can only be gained by using the techniques presented in Chapter 22, "Multi-
Application Testing."
Connecting to a target machine
Two ways to establish
a connection
There are two ways to establish a connection to a target Agent from SilkTest
running in the host: as a runtime option or in a script.
As a runtime option: You can specify the target's name in the host's
Runtime Options dialog before you run a script or suite. This is sufficient
when you are connecting to only one Agent. If you have been testing a script
by running SilkTest and Agent on the same system, you can then test the
script on a remote system without editing your script by using this method.