Difference between Desktop, Client Server Testing and Web Testing

In this post, I am gonna give an answer to reader's question.
There was one question asked by Srividya:

Q.What is the difference between client-server and Web Testing?
Vijay: Well Srividya I would like to add one more testing type i.e Desktop Testing in this discussion. So now we have three testing types Desktop application testing, Client server application testing, and Web application testing.

Each one differs in the environment in which they are tested and you will lose control over the environment in which application you are testing, while you move from desktop to web applications.

Desktop application runs on personal computers and workstations, so when you test the desktop application you are focusing on a specific environment. You will test complete application broadly in categories like GUI, functionality, Load, and backend i.e DB.

In the Client-server application, you have two different components to test. The 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 Intranet networks. You are aware of a number of clients and servers and their locations in the test scenario.

The web application is a bit different and complex to test as tester don't have that much control over the application. The 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.

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.

I think this will have an idea of all three testing environment. Keep in mind that even the difference exists in these three environments, the basic quality assurance and testing principles remain the same and applies to all.

Recommended Reading

133 thoughts on “Difference between Desktop, Client Server Testing and Web Testing”

  1. Hi SUREKHA

    here is Your answer

    Test engineer and Quality Engineer are not same

    Test Engineer : Who finds the defect/bugs.

    Qulaity engineer : Who finds the defects with respect to Quality factors

    we can find lot of difference between Test engineer and Quality engineer while working with the application in a real time environment.

    iam giving the answers with my extensive experience in Manual Testing for over more than four years in Software testing and Quality management.

    Thanks
    Chandeeswararao

  2. Hi SUREKHA

    here is Your answer

    Test engineer and Quality Engineer are not same

    Test Engineer : Who finds the bugs.

    Qulaity engineer : Who finds the Bugs with respect to Quality factors

    we can find lot of difference between Test engineer and Quality engineer while working with the application in a real time environment.

    iam giving the answers with my extensive experience in Manual Testing for over more than four years in Software testing and Quality management.

    Thanks
    Chandeeswararao

  3. Hope this helps

    Test engineer and Quality Engineer –

    Test Engineer : A Software Tester who tests applications
    or products. This is product oriented

    Quality Engineer: monitors the Process of the organisations like compliance in testing or development process. This is Process oriented

  4. hi all
    this is daya can anybody explain me what is client server and web application? because here is an article on client server and web application but this is very confusing .pls reply me on same
    u can reply me on my id daya81@gmail.com

  5. @jaiprakash chaudhary
    hey buddy..just use Google for all this u shd always so some b4 posting any question..
    hug lck happy surfing

  6. Hi,
    I have 1 year experience in manual testing of web applications in a company, currently I have joined another company where I am testing a desktop application.
    I wanted to know ,Will this affect scope of my carrer in testing in any way, that I have shifted from one form of testing to a completely different one, where there are no servers or databases,etc involved. ??

  7. Hi All

    Pleased to say that the Site is so help full for the testers. thanks for sharing such a good knowledge.

    I Have a query while going through the site, i found that the Load testing will be done on the desktop application under section “Difference between Desktop, Client server and Web testing” can any one help me to know more about, how to do Load testing on the desktop application.

    If we can do so … please let me know how to do a Load testing on the calc application or some other application which are windows based application.

    Thanks & Regards,
    Surender

  8. Hi,

    I think the diff b/w client server application and web application listed is based on partial programming and partial testing.

    Actually i diff based on programming and testing,

    First Programming Level explanation:

    The different type of application are,
    1. Console application
    the old days bank software/ supper market software, where there is no mouse (i.e NO GUI – Graphical user interface)

    2. Windows application
    The independ software such as calender, Library management system on stand alone system, task scheduler, etc

    3. Web application
    The application comes with HTTP or HTTPS, all internet site and online apps are web application.

    4. Mobile application
    The software or games used in our mobile phones

    5. Web services
    The application which support windows and web application.

    The above mentioned application can developed based on diff technologies(ASP, ASP.Net, Php, Java, VB, C, C++, VC++, Script lang and more…).

    This are the application we have, in which how we classify the application as client side/ server side.

    For Windows Application:

    what is client side?
    The program which stores in our own PC and execute in our own PC.

    what is Server side?
    The program which stores in our own PC but the script execute on server.

    For Web Application:

    what is client side?
    The program which stores in on server and execute in our own PC and result displayed in our own PC.

    what is Server side?
    The program which stores in on server and execute on server and result displayed on client.

    Based on this only we classified the application.

    Now diff based on Testing,

    Testing Level explanation:

    1. White box testing:
    the programmer will test based on the requirement, Tester is not allowed to do white box testing for client server apps even though he/she have coding knowledge. The programmer will write the test case and unit testing is followed.

    2. Black Box Testing:

    This is the part we concentrate , here only we have the confusion such as,
    what is application given?
    where to start testing/
    when to stop testing?
    How to cover all area?
    What are risk factor involved?
    etc.,

    1. How to identify the application?

    Client application:
    The application is independent and can run in stand alone machine(Our own PC)

    Server application:
    The application is any internet site or online system comes with testing URL.

    Client Server application:
    The application depend on local network or internet.

    2. Where to do testing?

    All the testing are done in client PC only. we are restricted to do testing in server for risk and security authentication reason.

    Windows Apps: Run purely on Client PC

    Web Apps: Internet explorer/ Firefox tools are used in client PC to connect to server.

    Client server application: client tool run in client PC which depend on Server tool run in server. The local area network apps is best suite example for client server apps.

    3. Where to Start testing?
    Its based on requirement, upto my experience start the testing where your functionality of the application starts.

    4. When to stop testing?
    Once all the modules are navigated, all the pages are opened, all the button are clicked atleast once and one flow through the system.

    Testing is not a course or job, Its vision where the creators are tied together.

    Any queries related to my topics, pls let me know.

    Thanks & regards,
    Raja,
    rajamurugesh.b@gmail.com

  9. #71,
    Hi Shweta,

    Pilot Test is a simple TRAIL RUN.

    A test of something such as a proposed manufacturing process to discover and solve problems before full implementation.

    For Example,

    1) If we want to automate any application, lets say, we have 500 test cases to automate, first we will automate 10 different test cases and prove youself that these are working fine. Then we will showcase this to our manager and get the approval for automating the rest of the test cases (490 test cases).

    2) When a software is produced and then deployed in production server, developers do a test run of the product before deploying the same. This process is known as Pilot Testing.

    You can also call it as a PoC – Proof of Concept.

    Hope this helps,

    Regards,
    VijayD

  10. Hello All. This site is very useful. All the answers are very clear and suggestions are good. I appreciate you people for giving the answers by taking time from your busy lifes. ITs really great job.

  11. Hi All,

    Can anyone please tell me any functional testing tool for a desktop application. I have a desktop application and I want to do the functionality testing using any open souce automation tool. That must have the recording-playback features in it. Plz let me know ASAP, its urgent.

    Thanks.

  12. Hi Vijay,
    I am a new user of this site and i found it very useful for me. I have one query, An application having SOA architecture is 2 tier or 3 tier appliaction?

  13. Hi VijayaLakshmi
    GUI Testing focus on Controls (like Push buttons, Combo Boxes, Test Boxes, List Boxes, Check Boxes, Radio Buttons, Scroll bars, Look and feel of application) to explain brief i am using Windows Calculator as an example.
    * In the Calculator (windows standerd) all the number buttons (from 1-9) are same in size. if not this is a GUI error
    * Number buttons should be arrenged properly like 1 then 2 then 3. if 3 is arrenged in between 1 and 2 this is also GUI Error
    * Tester will find this type of defects (as above) in GUI Testing (Look and feel, Colour, Controls are visible or not, Controls are not overlapped)

    * Functionality : if the output is wrong/right after calculated results this is Functinoal Testing
    * Ex: 2 x 3 = 6 this is correct but after pressing 2 * 3 then results are showing wrong (Say-5) this is Functionality testing

    One more example for Functionality Testing:
    A Functional Specification Document prepared by mentioning
    ‘All CLOSE buttons should toggled(changed) to CANCEL button’ after any thing entered in to NAME Text box
    * Just assume there us button name ‘CLOSE’ in an application containing NAME text box
    * you entered something into NAME text box but CLOSE button is not changed as ‘CANCEL’
    * As per the FSD the button name changing is a functionality. But it is not happening in the application so this is a Functional Error
    * Can find this types of defects in Functional Testing

  14. I want to know how to test a Desktop application and a website on different operating systems? Because it is not possible to have all the operating system. Are there any companies which offers this type of testing services.

  15. hi i have completed my ug inB E(CSE),now i am doing testing courses,i have to present a topic on CLIENT SERVER TESTING suggest me what is clientserversystem, how it is implemented and how testing can be done on client server software.
    Regards
    Durga.

  16. 1. White box testing:
    the programmer will test based on the requirement, Tester is not allowed to do white box testing for client server apps even though he/she have coding knowledge. The programmer will write the test case and unit testing is followed.

    2. Black Box Testing:

    This is the part we concentrate , here only we have the confusion such as,
    what is application given?
    where to start testing/
    when to stop testing?
    How to cover all area?
    What are risk factor involved?
    etc.,

Leave a Comment