Client Server Testing

Projects are divided into two types of architecture:
* 2 tier applications
* 3 tier applications
CLIENT / SERVER TESTING
This type of testing usually being done for 2 tier applications, we will test for front-end and backend modules.The application launched on front-end will have forms and reports with the help of which we can monitor and manipulate the data.
E.g: The front end applications developed in Visual Basic, VC++, Core Java, C, C++, C#, Dot net etc. The back end applications will be use MS Access, SQL Server, Oracle, Sybase, Mysql etc.

The tests performed on these types of applications would be
- UI testing
- Manual testing
- Functionality testing
- Compatibility testing & configuration testing

WEB TESTING
This is done for 3 tier applications (developed for Internet / intranet )
For web testing we will use browser [ Mozilla, Opera, Netscape, IE etc] and database server.The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript, AJAX etc. Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, PHP etc. (All the manipulations are done on the web server with the help of these programs developed).The data base server would be having oracle, sql server, mysql etc. (All data is stored in the database available on the data base server)

The tests performed on these types of applications would be
- User interface testing
- Functionality testing
- Security testing
- Browser compatibility testing
- Load / stress testing
- Interoperability testing/intersystem testing
- Storage and data volume testing

Desktop application:
1. Application runs in single memory (Front end and Back end in one place)
2. Single user only

Client/Server application:
1. Application runs in two or more machines
2. Application is a menu-driven
3. Connected mode (connection exists always until logout)
4. Limited number of users
5. Less number of network issues when compared to web app.

Web application:
1. Application runs in two or more machines
2. URL-driven
3. Disconnected mode (state less)
4. Unlimited number of users
5. Many issues like hardware compatibility, browser compatibility, version compatibility, security issues, performance issues etc.
As per difference in both the applications come where, how to access the resources. In client server once connection is made it will be in state on connected, whereas in case of web testing http protocol is stateless, then there comes logic of cookies, which is not in client server.

For client server application users are well known, whereas for web application any user can login and access the content, he/she will use it as per his use.So, there are always issues of security and compatibility for web application.