Functional Testing of a Web Application: a Complete Checklist

No votes yet.
Please wait...

Before pushing a project to production, a tester should not only follow specification requirements but also take into account the big importance of functional specification that can be applied to software.

Therefore, to not be afraid to push a project to independent testing, you should perform functional software testing on the basis of a checklist. Further, we’ll talk about it.

Functional Testing Checklist

Functional Testing Checklist

1 — testing each form


  • A user account has already been created;
  • A user has registered for the first time;
  • A user is blocked on a website and has no possibility to register for the second time.


  • A user account with the given password and login has been created;
  • A user with the given login doesn’t exist;
  • A user account has been created but his/her password is incorrect;
  • Validation of login fields (numeric fields, alphabetic fields, fields for numeric, alphabetic values, and special symbols).

Testing and validating all the required fields.

Testing feedback forms and correct work of links of Terms of Use.

2 — search

  1. Search results are correct and redirecting to details pages works properly;
  2. A user sees a correct message on no result;
  3. A search field is empty by default;
  4. A search field accepts either numeric/alphabetic values or special symbols.

3 — fields

  1. Fields with numeric values: letters should not be entered but even if so, a user should see the corresponding message;
  2. A value with a fraction;
  3. Negative values;
  4. Dividing by 0 is displayed correctly;
  5. Checking if fields use and accept special symbols;
  6. Testing the field size to check that the entered text doesn’t go over the borders.

4 — filters

  1. Testing functional settings of sorting;
  2. Work with filters with correct and incorrect results;
  3. Sorting by category, section, and block;
  4. Sorting by a search range;
  5. Information is displayed in a form of a dropdown.

5 — work with DevTools

  1. Testing for errors in a console;
  2. Checking that current styles are uploaded;
  3. Checking if all images and graphical elements are displayed.

6 — testing pop-ups

  1. Testing all text pop-ups;
  2. Verification of the messages for updating and deleting;
  3. Text messages on errors in case of incorrect input.

Leave A Comment