Skip to content

Latest commit

 

History

History
22 lines (14 loc) · 1.17 KB

framework-scope.md

File metadata and controls

22 lines (14 loc) · 1.17 KB

Framework Scope

Supported Deeply

Framework Status What is covered
Playwright First-class Generation, static review, failing-test fixes, locator guidance, web-first assertions, auth, network waits
Cypress First-class for review and failing-test fixes Static review, retryability, cy.intercept, cy.session; e2e-debugger flake check and test-only repair

Not In Scope Today

Puppeteer is intentionally not listed as supported automation. The general review ideas still apply, but the repository does not currently ship Puppeteer-specific grep patterns or eval fixtures.

Why Keep The Scope Narrow

E2E failures are framework-specific. A broad checklist that claims to support every runner usually misses the sharp edges that matter: Playwright web-first assertions, Cypress command retryability, framework-specific auth/session setup, and framework-specific report artifacts.

New framework support should include all of the following before it is advertised:

  1. Grep patterns or mechanical checks.
  2. At least one eval file with true positives and false positive guards.
  3. README and marketplace metadata updates.