A starting point: adapt these to your app. This page lists 14 test cases for forms and field validation, each with numbered steps and an expected result, and gives them to you as an Excel workbook, a CSV file or Markdown.
How to use it#
- Read the cases on this page. Each is marked Positive (the normal path), Negative (wrong input or a refused action) or Boundary (at or just past a limit).
- Select Download .xlsx for a workbook with a How to use tab and a tab of the cases, with Status set to Not run and blank rows for your own.
- Or select Download .csv to import the cases into another tool or a shared sheet, or Download .md to paste them into a wiki, a pull request or a test plan.
- Remove what does not apply to your app, change the steps to match your screens, and add what is special about yours.
What the cases cover#
Required fields left empty or holding only spaces, text exactly at a field's maximum length and one character over it, letters in a number field, an email in the wrong format and an impossible date. They check that a valid form is sent once even when the button is pressed twice, that what was typed survives an error, and that names such as Zoë Ångström or 山田太郎 are saved exactly. Text that looks like HTML must show as text. Errors must be announced to screen readers and reachable from the keyboard, and Cancel must discard changes.
Why these matter#
Forms are where users give you data, so their faults turn into bad records, double orders and support tickets. Validation that only works for typical input fails the people with long names, other alphabets or a screen reader. Writing them down once, with expected results someone else can check, turns a quick look before a release into a repeatable check.
What they do not cover#
These are generic cases. They do not know your app's rules, its other ways in, or its edge cases, so they are not full coverage. Read each expected result against how your app is meant to behave: some apps deliberately differ, and that is a decision to confirm, not a failure.
Questions#
Do these cover every form case?#
No. They are a starting point; adapt them to your app.
Can I edit them?#
Yes. Download the spreadsheet or the Markdown and change anything.
Is this free?#
Yes, with no account. Use the cases in your own plans and tools.
Can these run automatically?#
Not from this page; they are written for a person to follow. Each one is specific enough to automate later with the test tool your team uses.