Web Application Testing Checklist - Part 3
Date Published: 02/08/2018
While testing the web or desktop (windows form) application, it is very important to consider given below testing types and checklist mentioned in each testing type. This checklist is almost applicable for all types of web and desktop application depending on the business/client requirements.

Compatibility Testing

What is Compatibility testing? 

  • Compatibility testing is used to determine if your software is compatible with other elements of a system with which it should operate, e.g. Browsers, Operating Systems, or hardware.
  • What is the purpose or Goal of Compatibility testing? 
  • The purpose of Comp ability testing is to evaluate how well software performs in a particular browser, Operating Systems, hardware or software.
  • What should be tested in Compatibility testing?
  • Test the website in different browsers (IE, Firefox, Chrome, Safari and Opera) and ensure the website is displaying properly.


  • Test the HTML version being used is compatible with appropriate browser versions.


  • Test the images display correctly in different browsers.


  • Test the fonts are usable in different browsers.


  • Test the javascript code is usable in different browsers.


  • Test the Animated GIF's across different browsers.



Tool for Compatibility Testing 

Spoon.net: Spoon.net provides access to thousands of applications (Browsers) without any installs. This tool helps you to test your application on different browsers on one single machine. 


Database Testing

What is Database Testing? 

  • In Database testing, backend records are tested which have been inserted into the web or desktop applications. The data which is displaying in the web application should match with the data stored in the Database.
  • To perform the Database testing, the tester should be aware of the below mentioned points: 
  • The tester should understand the functional requirements, business logic, application flow and database design thoroughly.
  • The tester should figure out the tables, triggers, stored procedures, views and cursors used for the application.
  • The tester should understand the logic of the triggers, stored procedures, views and cursors created.
  • The tester should figure out the tables which get affected when insert, update and delete (DML) operations are performed through the web or desktop applications.

With the help of the above-mentioned points, the tester can easily write the test scenarios for Database testing. 

What should be tested in Database Testing? 

  • Verify the database name:  The database name should match the specifications or requirements.


  • Verify the Tables, columns, column types and defaults: All things should match the specifications/database design. 


  • Verify whether the column allows a null or not.


  • Verify the Primary and Foreign key of each table.


  • Verify the Stored Procedure: (Advanced)


  • Test whether the Stored procedure is installed or not. (Advanced)


  • Verify the Stored procedure name. (Advanced)

  • Verify the parameter names, types and number of parameters. (Advanced)


  • Test the stored procedure by deleting some parameters. (Advanced)


  • Test when the output is zero, the zero records should be affected.


  • Test the stored procedure by writing simple SQL queries. (Advanced)


  • Test whether the stored procedure returns the values. (Advanced)


  • Test the stored procedure with sample input data. (Advanced)


  • Verify the data gets properly saved into the database after each page submission.


  • Verify the data if the DML (Update, delete and insert) operations are performed.


  • Check the length of every field: The field length in the back end and front end must be same.


  • Verify the encrypted data in the database e.g. Password, Credit Card info etc.


  • Verify the database size. Also, test the response time of each query executed. (Advanced)


  • Verify the data displayed on the front end and make sure it is same on the back end.


  • Verify the data validity by inserting the invalid data in the database.


Keywords: Web Application Testing Checklist, Web Application UI Elements, Website Controls tutorial, Website UI controls