feat(playwright): @humanjs/playwright/test — a Playwright Test fixture with a ready human

[totigm]

What & why

QA users currently hand-roll createHuman(...) in every spec. This adds a Playwright Test fixture on the @humanjs/playwright/test subpath so they don't have to:

import { test, expect } from '@humanjs/playwright/test';

test('checkout', async ({ human, page }) => {
  await human.goto('/cart');
  await human.click('Checkout');
  await expect(page).toHaveURL(/success/);
});

The human fixture is bound to the test's page and defaults to seed = the test title (deterministic per test) and speed = instant in CI / humanized locally — the pattern we already document, now automatic.

Customize per file or per project:

test.use({ humanOptions: { personality: 'distracted', speed: 'human' } });

Packaging

• New src/test/ module → second tsup entry (dist/test.*) → ./test export.
• @playwright/test is an optional peer dependency (peerDependenciesMeta) — only the /test subpath imports it; the package root stays free of the test runner. publint --strict is clean and the subpath resolves correctly from a consumer (dist/test.cjs).

Docs

Root README "In tests", the package README, and the skill's CI/determinism section now lead with the fixture (explicit createHuman shown as the alternative).

Tests

Colocated fixture.test.ts asserts the subpath builds and re-exports a usable test (with .extend/.use) + expect — the runtime fixture behavior (seed/CI) is exercised by Playwright Test itself, not vitest. Gate green: lint · typecheck 9/9 · tests 8/8 · build 6/6 · check:exports (publint) 11/11.

Changeset

minor for @humanjs/playwright, patch for @humanjs/skill.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
humanjs	Ready	Preview, Comment	Jun 2, 2026 5:11pm