What is the difference between Desktop application testing and Web testing

Showing Answers 1 - 8 of 8 Answers


  • Jun 29th, 2006

Desktop testing is standalone testing Web testing is related to Client-Server

  Was this answer useful?  Yes


  • Jul 7th, 2006

Web testing needs to have many testings like usability, GUI, Load testing.

Testing URLs.

Desktop need not worry about number of users, etc.

  Was this answer useful?  Yes


  • Aug 7th, 2006

Desktop application is nothing but testing windows/standalone application where as webtesting is testing the web application like links,GUI,usability,load etc

  Was this answer useful?  Yes


  • Jan 25th, 2007

To be simple : Testing the application like MS Word or Excel sheet is a Desktop Application. Any thing which we use browser to acess the application like yahoo, gmail, net banking come under the Web Testing.

Surendra Reddy
Ness Technologies

Calculator, word, excel are few examples of Desktop Application

Online Trading Account, Online Banking, Yahoo are few examples of web application.

Desktop applications need Application’s exe so that it can be installed on Local Machine Web application need Browsers to be installed on Local Machine and to access we need URL

Desktop application is a standalone application (1 tier)
Web application is a client server application (3 tier)

While testing desktop application we consider functionality testing, database testing, GUI, regression testing etc but whereas while testing web application we not only consider the above but also we consider load/performance testing, links, compatibility testing etc

Desktop Application is a 2-tier architecture is a client/server architecture , where a request to do some task is sent to the server and the server responds by performing the task.where as a Web Application is a 3-tier has client, server and database. Where the client request is sent to the server and the server in turn sends the request to the database. The database sends back the information/data required to the server which in-turn sends it to the client.

  Was this answer useful?  Yes


  • Aug 23rd, 2011

Desktop application testing is a single user can do at a time, but web testing is shared by one or more than one user can able to test at the same time.

  Was this answer useful?  Yes

Priya kanhere

  • Sep 11th, 2011

In desktop application we need to test -

  • Functional Testing
  • Performance Testing
  • UI Testing
  • Usability Testing
  • Compatibility Testing (Hardware/Software)
  • Multi Language Support Testing
  • Installation Testing
  • Load Testing
  • Stress Testing
  • Compatibility Testing
  • Regression Testing (Automation support)
  • Exploratory Testing
  • Smoke Testing
  • User Acceptance Testing
  • Database Testing
  • Beta Testing

In Web testing we need to test -
1) Functionality Testing:
  • Test the outgoing links from all the pages from specific domain under test.
  • Test all internal links.
  • Test links jumping on the same pages.
  • Test links used to send the email to admin or other users from web pages.
  • Test to check if there are any orphan pages.
  • Lastly in link checking, check for broken links in all above-mentioned links.

2)Test forms in all pages:
  • First check all the validations on each field.
  • Check for the default values of fields.
  • Wrong inputs to the fields in the forms.
  • Options to create forms if any, form delete, view or modify the forms.

3)Cookies testing
4)Validate your HTML/CSS
5)Database testing
6)Usability Testing
7)Compatibility Testing:
  • Browser compatibility
  • Operating system compatibility
  • Mobile browsing
  • Printing options

8)Web Load Testing
  • Web Stress Testing

9) Security Testing:
  • Test by pasting internal url directly into browser address bar
    without login. Internal pages should not open.
  • If you are logged in using username and password and browsing
    internal pages then try changing url options directly. I.e. If you are
    checking some publisher site statistics with publisher site ID= 123. Try
    directly changing the url site ID parameter to different site ID which is
    not related to logged in user. Access should denied for this user to view
    others stats.
  • Try some invalid inputs in input fields like login username,
    password, input text boxes. Check the system reaction on all invalid
  • Web directories or files should not be accessible directly unless
    given download option.
  • Test the CAPTCHA for automates scripts logins.

  • Test if SSL is used for security measures. If used proper message
    should get displayed when user switch from non-secure http:// pages to
    secure https:// pages and vice versa.
  • All transactions, error messages, security breach attempts should get
    logged in log files somewhere on web server.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions