The content we see on the web pages has a strong impression on its user. If these contents are not satisfactory to him/her, he/she may not visit the web page again. Check the completeness and correctness, properties of web application content. Check that certain information is available on a given web page, links between pages exist, or even check the existence of the web pages themselves (completeness property). Furthermore, web application content may need to be checked against semantic conditions to see if they meet the web document (correctness property). Therefore the contents should be correct, visible, flexible to use, organized, and consistent.

This type of testing targets the testing of static and dynamic contents of web application. Static contents can be checked as a part of verification. For instance, forms are an integral part of any website, Forms are used to get information from users and to keep interacting with them. First, check all the validations on each field. Check for the default values of fields and also wrong inputs to the fields in the forms. Options to create forms if any, delete, view, or modify the forms must also be checked.

Static testing may consider checking the following points:

1. Various layouts.
2. Check forms for their field validation, error message for wrong input, optional and mandatory fields with specified length, buttons on the form, etc.
3. A table is present and has the expected number of rows and columns and pre-defined properties.
4. Grammatical mistakes in text description of web page.
5. Typographical mistakes.
6. Content organization.
7. Content consistency.
8. Data integrity and errors while you edit, delete, and modify the forms.
9. Content accuracy and completeness.
10. Relationship between content objects.
11. Text contents.
12. Text fragments against formatting expectations. This differs slightly from simple text checking in that the formatting tags can be located loosely on the page as opposed to a fixed string for text content.
13. Graphics content with proper visibility.
14. Media contents to be placed at appropriate places.
15. All types of navigation links internal links, external links, mail links, and broken links to be placed at appropriate places.
16. All links on a web page active.

There may also be dynamic contents on a web page. Largely, dynamic testing will be suitable in testing these dynamic contents. These dynamic contents can be in many forms. One possibility is that there are constantly changing contents, for example, weather information web pages or online newspaper. Another case may be that web applications are generated dynamically from information contained in a database or in a cookie. Many web applications today work interactively in the manner that in response to a user request for some information, it interacts with some DBMS , extracts the relevant data, creates the dynamic content objects for this extracted data, and sends these content objects to the user for display. In the same manner, the information can be generated dynamically from cookies also, that is, dynamic content objects for cookies are also there.

The problem in the design of these dynamic contents is that there may be many errors due to its dynamic behavior. Therefore, testing of these dynamic contents becomes necessary to uncover the errors. Changing contents on a web page must be tested whether the contents are appearing every time in the same format. Moreover, there is consistency between the changed content and static content.

Test all database interface-related functionality for all dynamic content objects. Check if all the database queries are executing correctly, data is retrieved correctly, and also updated correctly. Load the testing or performance testing can also be done on database.

Cookies are small files stored on the user machine. These are basically used to maintain the session, mainly the login sessions. The testing of the entire interface with these cookies must also be tested. Test the application by enabling or disabling the cookies in browser options. Test if the cookies are encrypted before writing to user machine. Check the effect on application security by deleting the cookies.