Current

15 — Frontend Testing and Acceptance

Status: Active release gate

Required test layers

  1. Contract tests for discovery, entities, projections, capabilities, approvals,
    marketplace installations and normalized errors.
  2. Component tests for loading, empty, partial, stale, unauthorized, conflict
    and approval states.
  3. Integration tests for tenant switch, role change, connector activation,
    entity CRUD, Four Buttons and governed execution status.
  4. End-to-end tests against Development and isolated Customer Zero Platform
    deployments.
  5. Accessibility and responsive checks for desktop, tablet and mobile.

Stop-ship criteria

  • Browser directly calls a database, provider, credential service, Hermes or
    internal MCP Pool.
  • A cross-tenant record, installation, cache entry or event becomes visible.
  • A department/industry selection changes physical storage rather than
    projection configuration.
  • Twin executes or writes truth without exact human approval.
  • UI reports success before the Platform reports an accepted state.
  • Public MCP exposes anything other than the governed 19-tool contract.
  • The Plugin claims it can scrape the host's app registry/credentials, or the
    MCP package lacks a functional browser Workbench/fallback path.
  • Demo/seed fallback appears in Customer Zero or Production without an explicit
    development-only flag.

Evidence

Release evidence records build/version, environment, tenant fixture, test
results, accessibility report, screenshots for critical states, API trace IDs
and unresolved waivers. Customer Zero data or credentials are never copied into
Customer Production as test fixtures.