Test Case Categories
Date Input Testing - Key Test Cases for Validating Date Fields and Formats
Testing date input fields is crucial for ensuring users can enter and save valid dates in the correct format. This guide includes essential test cases for validating date formats, input restrictions, leap year logic, minimum and maximum date ranges, and edge cases like invalid day or month values. Use these test cases to make sure your date fields handle both manual input and system logic reliably.
| Nr | Test Idea | |
|---|---|---|
| 1 | Check the parent page testcases for general input field testing guidelines | |
| 2 | Check what should be the correct format for entering the date | |
| 3 | Check if you can save for the first time without adding a date to the field | |
| 4 | Check that only characters needed for date entering would be allowed to enter/save to the field | |
| 5 | Check what happens when you erase existing date and save empty field | |
| 6 | Check if there should be a minimum or maximum date that can be entered | |
| 7 | Check what should be the minimum and maximum year that is allowed to be saved | |
| 8 | Check what happens if the user enters 01 for the day value | |
| 9 | Check if February 30 or 31 can be entered/saved to the field - should be invalid date | |
| 10 | Check if you can enter 0 or 13 for month value | |
| 11 | Check if you can enter 0 or 32 for day value. Check that specific month would have correct maximum day values | |
| 12 | Check how easy it is to remove date value from the field | |
| 13 | Check if date validation is correct also for leap year | |
| 14 | At date entering, if the validity of the date depends from current date then check that it would not block form saving later on when the date becomes invalid for entering (but not for displaying) |