Testing CLIENT – SERVER application :-

Ex – Yahoo messenger, Gtalk, ATM

Here, we consider the example of Gtalk :-

It requires 2 software – client software and server software.

Here, Gtalk s/w is the client s/w and Google server is the server s/w.

The main use of server s/w is,

·         Server is used to communicate the information

·         To store the information

Here, we 1^st download Gtalk into the client software, the s/w is installed from the server. Gtalk is installed in the client server. It then displays the username and password page (Login page). Once the client enters the username and password and submits, the request will be sent to the server, it will send a response to display the Homepage. The response is coming from the client server itself. The client displays the next window.

When we enter the information and submit, it goes to the Google Server and stores information and sends a response. The client server displays the next window because of the executable Gtalk. Exe file on the client’s PC.

The calendar, contacts etc and all other features of the Gtalk will open from the client s/w only because he has already downloaded and installed the s/w before only.

Whenever we double-click on Contacts, the page/window will be displayed once we enter the details and submit, the request goes to the server and stores the information and response is sent back. 

Once the developer writes the program for Gtalk and server, he compiles and compresses,

·         Server s/w will be named as Gtalk.tar

·         Client s/w will be named as Gtalk.exe

This is saved in the folder as,

            D : // Builds / B01 / Gtalk.tar

            D : // Builds / B01 / Gtalk.exe

This is copied to QA ( test environment ) from Rex (development environment ) and pastes both the build. Gtalk.tar is untarred and install it in QA server

Then test engineer downloads and installs Gtalk.exe in their computer as well as the local computer. Now start testing all the features.

When a bug is detected, it can wither be in client s/w or server s/w. changes can be done in server s/w or client s/w.

There are cases where we can predict or may not predict where the defect is.

When the Test engineer is sending bugs to the developers, the developers will fix the bugs and add new features in either server s/w or client s/w or both.

When the new s/w build is sent to the Testing team. They will uninstall the server and installs the new server s/w. They will also uninstall the Gtalk in their computer and install new Gtalk because by adding new features, the previous Gtalk may not work properly.

Whatever OS is used by end-users, the s/w has to be tested in all Os(s). Ex – XP, Vista, Windows 7 etc

Testing the s/w in different OS(es) is called compatibility test.