Client/Server - Concurrent programming issues
directly on the server machine and is not a client application. For
example, administrative functions used for setting up the database.
exactly as it drives a client application. In addition, QA DBTester, a
companion product to SilkTest, provides direct access, using SQL, from a test
script to any database supported by ODBC drivers. These database functions
enable you to read and write database records without using the client
application. Thus you can verify client test results without assuming the
ability of the client to do that verification.
functions to help manage your testing process as follows:
database, submit an SQL statement, read data from the selected record(s) if
the SQL statement was SELECT, and subsequently disconnect from the
database. About a dozen of these functions allow you to access your
database's catalog tables.
online Help. They begin with the letters "DB_".
raised when you test applications on multiple machines and when you run
those tests in parallel. This section provides a conceptual understanding of
the issues and how to manage them. Chapter 21, "Implementing Client/
Server Testing" and Chapter 22, "Multi-Application Testing" explain specific
techniques and give coding examples.
you can do many of them using SilkTest's recording capabilities.
When you generate testcases for a multi-application or client/server
environment, you will have to do some 4Test coding to specify the