Positron Playwright E2E Testing

Purpose

Provides specialized knowledge and patterns for writing correct, reliable Playwright e2e tests that follow Positron's established conventions and avoid common mistakes.

Philosophy: What Makes a Good E2E Test

Prefer the smallest test that confidently protects the intended user-visible behavior. Do not add additional scenarios or assertions simply because they are easy to write -- extra setup, incidental checks, and duplicate assertions add maintenance cost and flake surface without adding confidence.

A good e2e test:

• validates observable user behavior, not implementation details
• exercises a complete workflow, not a fragment of one
• minimizes setup to what the regression actually needs
• remains deterministic -- no reliance on fixed waits, execution order, or leftover state
• isolates the single regression it protects, so a failure points at one cause

When to Use This Skill