Boundaries of test evidence

A test pass has the scope of its inputs and assertions. Treat evidence according to what actually ran.

Source versus runtime

Mocks isolate logic but do not establish provider mail delivery, database locks or browser history behavior. Compilation validates production output but does not establish a deployed worker schedule.

A financial helper can be correct while its mounted control sends the wrong account. Test the actual integration when behavior crosses those layers.

Browser timing

Use actual browser checks for delayed responses, long-lived dialogs, sign-out, Back and account changes. Include private portals, interactive guidance and reduced motion. A pure helper test cannot reproduce all restored-document timing.

Provider and database

Use authorized provider flows for session and email claims. A recovery API success means request acceptance, not delivered mail. Use actual database schedules for concurrency behavior and verify cleanup and ownership around synthetic fixtures.

Product capability

A helper module or reserved scope does not make a planned feature available. Complete-history export, self-service deletion and MCP transport remain planned until their actual supported flow exists.

Reporting a limitation

Name the specific unchecked boundary and the next acceptance needed. Avoid replacing it with a broad statement that everything works or nothing is usable. See test inventory and public roadmap.