{"slug":"business/15_FRONTEND_TESTING_AND_ACCEPTANCE","title":"15 — Frontend Testing and Acceptance","section":"business","sectionLabel":"Business","status":"current","type":"document","path":"business/15_FRONTEND_TESTING_AND_ACCEPTANCE.mdx","bytes":1666,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Active release gate\n\n## Required test layers\n\n1. Contract tests for discovery, entities, projections, capabilities, approvals,\n   marketplace installations and normalized errors.\n2. Component tests for loading, empty, partial, stale, unauthorized, conflict\n   and approval states.\n3. Integration tests for tenant switch, role change, connector activation,\n   entity CRUD, Four Buttons and governed execution status.\n4. End-to-end tests against Development and isolated Customer Zero Platform\n   deployments.\n5. Accessibility and responsive checks for desktop, tablet and mobile.\n\n## Stop-ship criteria\n\n- Browser directly calls a database, provider, credential service, Hermes or\n  internal MCP Pool.\n- A cross-tenant record, installation, cache entry or event becomes visible.\n- A department/industry selection changes physical storage rather than\n  projection configuration.\n- Twin executes or writes truth without exact human approval.\n- UI reports success before the Platform reports an accepted state.\n- Public MCP exposes anything other than the governed 19-tool contract.\n- The Plugin claims it can scrape the host's app registry/credentials, or the\n  MCP package lacks a functional browser Workbench/fallback path.\n- Demo/seed fallback appears in Customer Zero or Production without an explicit\n  development-only flag.\n\n## Evidence\n\nRelease evidence records build/version, environment, tenant fixture, test\nresults, accessibility report, screenshots for critical states, API trace IDs\nand unresolved waivers. Customer Zero data or credentials are never copied into\nCustomer Production as test fixtures.\n"}