Purpose

The purpose of this test case is to ensure that a web form meets the functional requirements for a proper user experience.

It does not make any assumptions about your business requirements.

Preconditions

• The form is functional and ready for testing.
• The page it is on is accessible via a URL.

Specifications and Steps

1. The initial state of the form should have no invalid warnings or error messages.
2. When you fill out the fields, it is permissible for the form to warn you when you leave a field in an invalid state. It should not warn you while you are still typing in the field.
   1. It is also permissible for no warning to be shown until you attempt to submit the form.
3. The form should give hints or instructions if it attempts to enforce specific formatting.
4. All form fields should have visible labels. The labels should also be programmatically connected to their fields. When you click on a label, it should focus on that field and you should be able to begin typing.
5. Ideally, the form should use autocomplete hinting for common fields related to name and address. Your browser should complete those for you automatically (this is dependent on your browser and if you’ve allowed it to save your contact information).
6. Required inputs should be marked, or some instructions should indicate that all fields are required.
7. Try navigating the form fields with your keyboard by using the Tab key to move to the next field, and Shift+Tab to move back. Note any failures.
8. For testing purposes, leave at least one field in an invalid state.
   1. For more thorough testing, you’ll want to test both invalid inputs and empty inputs on all fields.
      1. For instance, try putting some information in an email field that is not an email, but also test the field being empty.
9. When attempting to submit an invalid field and/or empty fields, the form should not submit, and the form should provide instructions on how to fix your errors.
10. If the form is for lead collection, it is required that you get explicit consent to send marketing via email to the customer. This consent is usually in the form of a checkbox, and the checkbox should be unchecked in its initial state. The form being unchecked is NOT A VALIDATION ERROR. This checkbox cannot be “required”.
11. Captcha functionality will vary, but note any Captcha-related errors you encounter.
12. When the field is in a valid state, submit the form.
13. Some forms may send their information and update the page you are on, while some forms will take you to a different page. Regardless of the functionality, any errors at this step should be detailed, and the test has failed.