Test plan

A feature tested only along the happy path looks finished, but it tends to break the moment a real user does something odd: leaves a field empty, pastes a huge chunk of text or comes in from an old phone. The bugs you do not look for are exactly the ones that reach production and come back as complaints.

This template gathers the QA checks to test a feature thoroughly before calling it finished, from the main flow to the edge cases and invalid inputs. It is not a list to tick a box, it is to find the problems yourself, calmly, before whoever uses it does.

What to check before calling it ready

These are the points the template brings, in the order worth covering them:

• Define the scope of the tests and what stays out
• Prepare the test data you will need
• Test the main flow, the path almost everyone will take
• Test the edge cases, those values right at the border
• Test invalid inputs and see they do not blow anything up
• Verify the error messages are clear and useful
• Test on different devices and screen sizes
• Check accessibility with keyboard and screen reader
• Review performance under load, not just with one record
• Log and report the bugs with steps to reproduce them
• Confirm the fixes once they are done

How it works in Foco

When you import it, Foco creates the "Testing" workspace with these checks in the List view, grouped by date so you see what to test today and what is left to cover. You tick each point as you check it and take nothing for granted too soon.

You can mark as important what cannot fail, assign to someone else the tests on devices you do not own and leave a voice note describing a strange bug right when you see it, so you can report it well afterwards.