What is the diffrence between web testing & web based
testing?
Answer Posted / subbu bhogireddy
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 front-end and backend.
The application launched on front-end will be having forms and reports which will be monitoring and manipulating data
E.g: 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 types of applications would be
- User interface testing
- Manual support testing
- Functionality testing
- Compatibility testing & configuration testing
- Intersystem 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 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
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 types of tests, which can be applied on this type of applications, are:
1. User interface testing for validation & user friendliness
2. Functionality testing to validate behaviors, i/p, error handling, o/p, manipulations, services levels, order of functionality, links, content of web page & backend coverage’s
3. Security testing
4. Browser compatibility
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 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 tests performed on these applications would be
1. User interface testing
2. Manual support testing
3. Functionality testing
4. Compatibility testing
5. Intersystem testing
Some more points to clear the difference between client server, web and desktop applications:
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 intentions.
So, there are always issues of security and compatibility for web application.
| Is This Answer Correct ? | 1 Yes | 1 No |
Post New Answer View All Answers
Why Equivalence Partitioning is called equivalence or what is the significance of equivalence term in ECP?
What type of questions will be asking for 2 years experience candidate in manual testing?
Can you explian $ pillar of Agile
in an online banking software,users are connecting to bankserver by login.This login module can take below inputs for user. a/c number prefix-3 digits but doesnot start with 0&1 a/c number sufix-6 digits number password-5to 10 chars alphanumerics in lowercase areacode-3 digits number but optional purpose- cheque deposit money trasfer mini statement bills pay After filling above fields,user can click submit button to connect to bank server.prepare test scenarios for online banking s/w login.
How a test engineer will convince a test lead when he didn't approve the bug as a report ???
I have 2 years of exp. in testing and looking for a change if any body knows, about any vacancy in testing then plz contact me on deepti_ac@yahoo.co.in
what is test scenario and test condition?
What is manual testing and what is it process?
What is error cusing tecnique
Hi, this is murthysharma. I need very urgently about some terms which are used in use cases? Plz give reply to me, if any body know, It is really very very urgent. 1. what is the difference between basic flow,exception flow and alternative flow? 2.what are non-functional requirements in use cases? 3.what are exceptions, special requirements, business rules, assumptions, constraints. Kindly give me with the example. Bcoz, I am very new to this use cases. thanks in Advance. Regards, M.MurthySharma
send the senario template
How to test an application if it was already developed and it is in the state of changing the functionality according to the customer requirement How to start testing in this situation. I got an application to test.It is a desktop application.It is still developing and started 8 months back.how can i start to test this application? Is it the right way to test it in "Random testing"? or writing the testcases from page one and executing them.i have an another responsibility that is I have to automate that application. can anyone tell me what is the process to test this application.
How do you scope, organize, and execute a test project?
hi friends i recently finished testing course in hyderabad.now am looking for a job in uk.i need help about the projects in interview point.can any one explain me abt banking project or credit card.like what are the problems faced in u r last project etc.
Explain the strategy for testing a Java application?