CRM explorer acceptance

Verification Boundary

Explorer journeys inspect contact and organization selection, visible columns and record outcomes reached through Platform query surfaces. This register groups 52 files with a common verification boundary; it does not register each file as an independent suite. Files and assertion sources remain explicit so an operator can select the group without losing the narrower proof boundaries.

What This Suite Proves

Explorer journeys inspect contact and organization selection, visible columns and record outcomes reached through Platform query surfaces. The structured bindings retain the previously recorded contributions. An unbound file supplies no newly asserted specification coverage. No execution result is claimed by this registration.

What It Does Not Prove

An explorer fixture or displayed label does not establish service filtering or freshness unless the individual assertion reads that result. A bound contribution is evidence for its assertions rather than certification of an entire composite scenario. Skipped or environment-dependent declarations remain visible in the source observations.

Real Dependencies and Test Doubles

The browser, sign-in and development APIs supply real record interactions. The acceptance harness uses run-marked data and cleanup callbacks; shared catalogue fixtures require exclusive scheduling. Individual tests can inject selected responses, which remain limited proof. The evidence list and per-file source observations identify the existing tests and their declared dependencies.

Must Not Be Doubled

Keep the browser actions and every API read claimed as real by a bound assertion. A supplied response must never be presented as a deployed persistence or authorization result.