What to test in your first full-stack project
Start with the behavior that would matter most if it broke: saving data, protecting access, and explaining failures.
Test the core flow
Submit valid input, verify the saved record, and reload. Check that the right user can retrieve it and another user cannot.
Check failure states
Try invalid input, a missing record, and a failed service request. The application should explain the problem and preserve work the user can recover.
Make checks repeatable
Automate the checks that protect important logic. Keep a short manual checklist for keyboard navigation and responsive layouts.