Test the Important Edge Cases

A small application still needs to handle ordinary mistakes gracefully.

Try these cases:

• click the Add Task button and close the modal without creating anything
• submit the form without a title if the title field is required
• drag a task onto its current column
• drag a task across more than one column before dropping it
• delete a task and then refresh
• create several tasks and refresh

Watch for duplicate cards, incorrect counts, unexpected navigation, and stale drag highlighting.

The goal is not to invent new behavior. Check that the behavior already taught in the course remains stable when the user does something slightly different from the ideal path.

Checkpoint

The application should remain usable in all of these cases. A failed edge case is a useful debugging clue: trace it back to the state change and the render that follows it.