E2E tests exist for the primary user flow
Why it matters
An E2E framework installed in devDependencies with no actual E2E tests is worse than not having one at all — it creates the impression of integration-level coverage that doesn't exist. Playwright, Cypress, and Puppeteer are designed to catch the class of bugs unit tests cannot: routing misconfigurations, broken form submissions, misconfigured auth redirects. A signup flow that works in isolation but fails end-to-end due to a missing CORS header or broken redirect will never be caught by unit tests. ISO-25010:2011 testability requires that critical user journeys be exercised as a system.
Severity rationale
High because missing E2E coverage for the primary user flow means complete-flow regressions — auth, checkout, signup — go undetected until a user reports them.
Remediation
Write one E2E test covering the primary user journey. It needs three things: navigation to the starting URL, form interaction, and an assertion on the resulting page state. Add it to e2e/ or tests/e2e/:
// e2e/signup.spec.ts
import { test, expect } from '@playwright/test'
test('new user can sign up and reach dashboard', async ({ page }) => {
await page.goto('/signup')
await page.fill('input[name=email]', 'new@example.com')
await page.fill('input[name=password]', 'P@ssw0rd123')
await page.click('button[type=submit]')
await expect(page).toHaveURL('/dashboard')
await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible()
})
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Test Reality Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · maintainability.testability — Testability (maintainability sub-characteristic)
Taxons
History
- 2026-04-18·v1.0.0·Initial import from ai-slop-test-theater·automated