playwright-testing
SkillWeb & browsingWrite end-to-end browser tests using Playwright.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the playwright-testing skill
What this skill tells your AI
The instructions your AI receives, as published by prairielearn/prairielearn in .agents/skills/playwright-testing/SKILL.md and read by ahel’s review.
New E2E tests should be created in apps/prairielearn/src/tests/e2e. Each test file should be named *.spec.{ts,tsx} and contain tests for a specific feature or user flow.
expect and test should be imported from apps/prairielearn/src/tests/e2e/fixtures.ts. These include fixtures to start the PrairieLearn server and provide an editable test course.
Prefer using selectors that use user-facing content, such as getByRole, getByText, and getByLabel. If that's impractical, consider using getByTestId instead. Add data-testid attributes or aria-label to page components when needed. Avoid using locator() with implementation details like CSS classes or IDs unless absolutely necessary.
Playwright e2e tests run fully in parallel (fullyParallel: true). Each test must be self-contained — set up its own state (users, enrollments, etc.) rather than relying on shared mutable state from beforeAll. Use the courseInstance fixture for the default course instance. Don't use module-level variables to share state between tests.
Signals
- GitHub stars
- 500
- Forks
- 391
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
playwright-testing-prairielearn- Source
- github.com/prairielearn/prairielearn