Tuesday 6 October 2015

Difference between Desktop,client server and Web based Application

Difference between Desktop,client server and Web based Application

Testing of desktop applications, client server application testing and testing of web applications. Everyone has a different environment in which to experiment and you lose your monitor an environment in which to test the application, when you go to the desktop Web applications.

Desktop application runs on personal computers and workstations, so when you test the desktop application that you are focusing on a particular environment. There will be a test of the complete application of classes, a graphical user interface, functionality, Load, and backend ie DB.

In client-server application has two distinct components to be tested. The application is loaded on the server while the application exe on every client machine. Usually are tested in categories like, GUI on both sides, functionality, load, client-server interaction, server. This environment is mostly used in intranets. We know the number of clients and servers and their locations in the test case.

Projects are broadly divided into two types of :
2 tier applications
3 tier applications


CLIENT / SERVER TESTING

This type of testing usually done for 2 tier applications (usually developed for LAN)
Here we will be having frontend and backend.
The application launched on frontend will be having forms and reports which will be monitoring and manipulating data Eg : applications developed in VB,VC++,Core Java,C,C++,D2K,PowerBuilder etc.,The backend for these applications would be MS Access, SQL Server, oracle, sybase, mysql, quadbase

The tests performed on these type of applications would be
- user interface testing
- manual support testing
- Functionality testing
- compatability testing & configuration testing
- intersystems testing

WEB TESTING
This is done for 3 tier applications (developed for Internet / intranet / xtranet)
Here we will be having Browser, web server and DB server.
The applications accessable in browser would be developed in HTML, DHTML, XML, JavaScript etc.,(we can monitor thru these applications)
Applications for the webserver would be developed in Adv Java, ASP, JSP, VBScript, JavaScript, Perl, ColdFusion, PHP etc.,
(all the manipulations are done on the web server with the help of these programs developed)

The DBserver would be having oracle, sql server, sybase, mysql etc.,
(all data is stored in the database available on the DB server)


The tests performed on these type of applications would be
- user interface testing
- Functionality testing
- security testing
- browser compatability testing
- load / stress testing
- interoperability testing/intersystems testing
- storage and data volume testing

A web-application is a three tier application.
This has a browser (monitors data) [monitoring is done using html, dhtml, xml, javascript]-> webserver (manipulates data) [ manipulations are done using programming languages or scripts like adv java, asp, jsp, vbscript, javascript, perl, coldfusion, php] -> database server (stores data) [data storage and retrieval is done using databases like oracle, sql server, sybase, mysql] .

The type of tests which can be applied on this type of applications are : 
1. User interface testing for validation & userfriendliness
2. Funtionality testing to validate behavious, i/p, error handling, o/p, manipulations, services levels, order of functionality, links, content of web page & backend coverages
3. Security testing
4. Browser compatability
5. Load / stress testing
6. Interoperability testing
7. Storage & data volume testing

a client-server application is a two tier application. 
This has forms & reporting at frontend (monitoring & manipulations are done) [ using vb, vc++, core java, c, c++, d2k, power builder etc.,] -> database server at the backend [data storage & retrieval) [ using ms access, sql server, oracle, sybase, mysql, quadbase etc.,]

the tests performed on these applications would be 
1. User interface testing
2. Manual support testing
3. Functionality testing
4. Compatability testing
5. Intersystems testing


No comments: