background image
<< Introduction to Client/Server Testing | Client/Server - The kinds of network testing you can perform >>
Client/Server - Client/server testing with SilkTest
<< Introduction to Client/Server Testing | Client/Server - The kinds of network testing you can perform >>
338
User's Guide
19 I
NTRODUCTION
TO
C
LIENT
/S
ERVER
T
ESTING
Client/server testing with SilkTest
also communicate across a network with remote devices and with a variety of
other applications. The step from testing a stand-alone application running on
a single PC or workstation to testing an application that runs on multiple
different platforms and communicates across a network with other
applications is a big one. Here are just a few of the testing methodology
problems raised by such a step:
·
Managing simultaneous automatic regression tests on different
configurations and/or platforms.
·
Ensuring the reproducibility of client/server tests that modify a server
database.
·
Verifying a client application's server operations independently without
relying on the application under test.
·
Testing the concurrency features of a client/server application.
·
Testing the intercommunication capabilities of networked applications.
·
Closing down multiple failed applications and bringing them back to a
particular base state (recovery control).
·
Testing the functioning of the server application when driven at peak
request rates and at maximum data rates (peak load and volume testing).
·
Automated regression testing of multi-tier client/server architectures.
Client/server testing with SilkTest
With SilkTest:
·
You can test an application that runs on a different machine than SilkTest.
·
You can test applications running on two or more machines at once.
·
You can test multiple different applications simultaneously.
QA DBTester provides an additional feature: You can access a server
database directly, thereby circumventing the untested database operations of
the application under test.
This section introduces the factors that make these features possible.
SilkTest architecture
Normal use of an application consists of a person manipulating a keyboard
and mouse to initiate application operations. The person is said to be
interacting with the GUI (Graphical User Interface). During SilkTest testing,
SilkTest interacts with the GUI to submit operations to the application
automatically. Thus SilkTest can simulate the actions of a person who is
exercising all the capabilities of an application and verifying the results of