background image
<< Client/Server Testing - Reporting distributed results | Client/Server Testing - Running tests on one remote target >>
Client/Server Testing - Incremental functional test design
<< Client/Server Testing - Reporting distributed results | Client/Server Testing - Running tests on one remote target >>
User's Guide
373
21 I
MPLEMENTING
C
LIENT
/S
ERVER
T
ESTING
Incremental functional test design
Elapsed time -- sorts results for all threads and all machines in event
order. This enables you to see the complete set of results for a time
period and may give you a sense of the load on the server during that
time period or may indicate a performance problem.
Machine --sorts results for all threads running on one machine and
presents the results in time-sorted order for that machine before reporting
on the next machine.
Thread -- sorts results for all tests run under one thread and presents the
results in time-sorted order for that thread before reporting on the next
thread.
Incremental functional test design
SilkTest simplifies and automates the classic QA testing methodology in
which testing proceeds from the simplest cases to the most complex. This
incremental functional testing methodology applies equally well in the client/
server environment, where testing scenarios should proceed from the
simplest functional testing of one instance of a client application, through
functional and performance testing of a heavily loaded, multi-client
configuration. Therefore, we recommend the following incremental
progression for client/server testing:
Perform functional testing on a single client application that is running
on the same system as SilkTest, with the server application on the same
system (if possible).
Perform functional testing on a single remote client application, with the
server application on a separate system.
Perform functional and concurrency testing on two remote client
applications.
Perform stress testing on a single client application running locally or
remotely.
Perform volume load testing on a configuration large enough to stress the
server application.
Perform peak load testing on a large configuration (to the limits of the
server, if possible).
Perform performance testing on several sets of loads until you can
predict performance.