CLIENT / SERVER TESTING
In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This environment is mostly used in LAN networks. You are aware of number of clients and servers and their locations in the test scenario .This type of testing is performed over 2-tier architecture or client-server architecture where client sends the request and server process it. If we look at the structure its simple but as a security perspective , the architecture is unsecure. Here we will be having front-end and backend.This has forms & reporting at front-end (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 application launched on front-end will be having forms and reports which will be monitoring and manipulating data
The backend for these applications would be any database from where the sate is fetched .As an example we can take MS Access, SQL Server, Oracle, Sybase, Mysql, Quadbase
The tests performed on these types of applications would be
– User interface testing
– Manual support testing
– Functionality testing
– Compatibility testing & configuration testing
– cross-browser testing
- Client server Interaction
WEB TESTING
Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Here we access web servers using web browsers .Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load 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 accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc. (We can monitor through these applications)
Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, 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 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
In client server application you have two different components to test. Application is loaded on server machine while the application exe on every client machine. You will test broadly in categories like, GUI on both sides, functionality, Load, client-server interaction, backend. This environment is mostly used in LAN networks. You are aware of number of clients and servers and their locations in the test scenario .This type of testing is performed over 2-tier architecture or client-server architecture where client sends the request and server process it. If we look at the structure its simple but as a security perspective , the architecture is unsecure. Here we will be having front-end and backend.This has forms & reporting at front-end (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 application launched on front-end will be having forms and reports which will be monitoring and manipulating data
The backend for these applications would be any database from where the sate is fetched .As an example we can take MS Access, SQL Server, Oracle, Sybase, Mysql, Quadbase
The tests performed on these types of applications would be
– User interface testing
– Manual support testing
– Functionality testing
– Compatibility testing & configuration testing
– cross-browser testing
- Client server Interaction
WEB TESTING
Web application is a bit different and complex to test as tester don’t have that much control over the application. Application is loaded on the server whose location may or may not be known and no exe is installed on the client machine, you have to test it on different web browsers. Here we access web servers using web browsers .Web applications are supposed to be tested on different browsers and OS platforms so broadly Web application is tested mainly for browser compatibility and operating system compatibility, error handling, static pages, backend testing and load 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 accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc. (We can monitor through these applications)
Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, 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 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
No comments:
Post a Comment