Free tool
What does your test plan forget?
Every plan covers the happy path, because that is the one you can picture. Paste yours and see which of the paths that actually break are missing — a refused permission, a declined card, a lost connection, an upgrade over the last build.
How it decides
It looks for evidence that each painful area was thought about at all, anywhere in the plan — a title, a step, an expected result. One mention counts. That is deliberately generous: a checker that cried wolf would be closed after one use, and a plan that mentions offline behaviour probably has someone who remembered it.
So a clean result means nobody forgot these exist. It does not mean they are tested well. The sixteen areas come from the bugs that reach users after a release looked fine: permissions, interruptions, migrations, money, empty states, roles, and the ones people only find on a train.