- Simplest Happy Case (an average, input string, without any errors or special conditions).
- Does it enforce input character set limitation ?
- †Does the accepted character set meet the minimum requirement for the field. For example a it might make sense for description to "™", "©", "®", etc.
- Does the accepted character set include unnecessary characters. For example a "#" in an email input field.
- Are validation rules enforced correctly ? For example payment amount in an Indian site my accept numbers with comma's like this 1,00,00,000 instead of 10,000,000. Sometimes an input field might accept "-username@domain.com"
- Is the validation rule exhaustive ?
- Is minimum length enforced correctly ?
- Does it trim spaces (leading and trailing) before processing data ? For example it should n't say illegal input for input with leading spaces.
- † Is the minimum length reasonable. For example if the minimum name length of a name is 5 or even 3 it could spell trouble because some folks have 2 character last names or worse just might want to use the initial of their last name.
- Is maximum length enforced correctly ? Does it accept maximum number of characters ? If it persists it somewhere, does it actually save all the characters and can you retrieve those correctly ?
- † Is the maximum length appropriate ? For example, should the maximum length for name be 200 characters ?
not considered here: security testing.
Email input fields: on top of the above rules here are some more
- plain vanilla email, like YourLogin@domain.com
- names with ".", like firstname.lastname@domain.com
- domain name with more than on segment, like firstname.lastname@host.subdomain.domain.com.cc
- hypenated names and domains firstname-lastname@some-hyphenated-domain.gov
- + aliases, like YourLogin+sortCoupons@domain.com
- very short email ab@bc.tv