Browser E2E Automation
Playwright setup and workflow coverage for the memory MVP.
Intertool uses Playwright for public, authentication, onboarding, and memory-lifecycle browser checks.
docker compose up -d postgres
pnpm test:e2e:install
pnpm test:e2eThe Playwright configuration migrates/seeds the local database, starts Fastify on port 3001, and starts Next.js in an isolated build directory on port 3317. DEV_AUTH_BYPASS=true is set only in those local processes; browser tests never depend on real OAuth.
Use PLAYWRIGHT_PORT to change the web port. Set PLAYWRIGHT_BASE_URL to test an already running target, or PLAYWRIGHT_REUSE_SERVER=true to intentionally reuse local processes.
Coverage
- public home, sign-in, docs, and LLM documentation endpoints;
- safe logout and callback normalization;
- guarded local sign-in;
- Alice creating, reviewing, sourcing, and explicitly publishing a memory;
- fresh-user onboarding entry;
- responsive desktop and mobile public surfaces.
Protocol-level integration tests separately verify MCP initialization/tool listing, Alice-to-Bob context retrieval, tenant isolation, lifecycle exclusions, token hashing/revocation, audit records, ranking, and compaction.
Prefer getByRole, getByLabel, and visible outcome assertions. Do not add test IDs when an accessible name can remain stable.
pnpm test:hooks exercises both client hook payloads, completion gates, local privacy, offline persistence, worker retries and configuration merging. The server integration suite covers the authenticated lifecycle API and private context isolation. These checks do not replace a real client installation and trust check.