Test the experience, not just the code
Check the important journeys before real people depend on them.
The idea
A passing build does not prove a useful product. Test functional behavior, usability, accessibility, data boundaries, and recovery from failure. Prioritize by how much harm a failure would cause.
Put it into practice
Walk through the core journey on phone and desktop. Try empty inputs, long content, keyboard navigation, slow connections, and failed requests. If there are accounts, test that one user cannot access another user’s data.
A summary tool needs to handle blank text, repeated submissions, an unavailable AI service, and a mistaken result. The user must be able to correct the output and keep their work.
Use AI thoughtfully
Ask AI for a risk-based test matrix. Convert the highest-risk cases into checks you can actually run. Treat generated test coverage as a proposal, not evidence of correctness.
Your checkpoint
Can the user complete the core job and recover safely from the most likely failures?
Write your answer to the checkpoint. Notes stay in this browser.