Index of every page on this site: llms.txt
All skills
corey-alix avatar

/playwright-testing-assistant

@e4fbc1d
Run it yourself

Provides guidance for implementing end-to-end tests using Playwright, following best practices for test structure, reliability, and maintainability.

  • 1 file
  • 2.7 KB
  • Updated 9 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/corey-alix/dwp-hours/playwright-testing-assistant

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈45 tokens for metadata: the name and description. ≈637 when used: this file.

Description uses 2.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈179 characters, or 2.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Playwright Testing Assistant

Description

Provides guidance for implementing end-to-end tests using Playwright, following best practices for test structure, reliability, and maintainability. Helps set up and maintain E2E test suites for the DWP Hours Tracker application.

Trigger

Activated when users mention Playwright testing, E2E testing, browser automation, test setup, or ask about testing frontend functionality, user workflows, or integration testing.

Test File Convention Validation

When refactoring test files, use E2E tests to validate that functionality remains intact:

  1. Pre-Refactoring: Run full E2E test suite to establish baseline
  2. Post-Refactoring: Run E2E tests to ensure no regressions
  3. Component-Specific: Target tests for modified components using grep patterns
  4. CI/CD Validation: Ensure tests pass in automated environments

Example: After removing inline attributes from test.html files, run E2E tests to confirm component initialization still works correctly.

Response Pattern

  1. Assess current testing setup and identify gaps in E2E coverage
  2. Recommend test structure following Playwright best practices (page objects, test isolation, descriptive naming, and test.step() for logical grouping of actions)
  3. Guide implementation of specific test scenarios with proper selectors and assertions
  4. Suggest debugging approaches for flaky tests and CI/CD integration
  5. Ensure tests align with project quality gates and TASKS/testing-suite.md requirements

Examples

  • "How do I set up Playwright tests for the login functionality?"
  • "Help me write E2E tests for the PTO submission workflow"
  • "My Playwright test is flaky, how can I fix it?"
  • "What's the best way to organize Playwright tests in this project?"
  • "How do I run Playwright tests in CI/CD?"

Additional Context

This skill integrates with the existing testing strategy defined in TASKS/testing-suite.md and follows Playwright's official best practices. Focuses on reliable, maintainable E2E tests that complement the existing Vitest unit testing setup. Prioritizes test stability, proper isolation, and clear reporting for CI/CD pipelines.

Understands and promotes the use of test.step() for organizing test actions into logical, reportable steps that improve test readability and debugging. test.step() allows nesting of steps, returns values from the step body, and supports options like box to point errors to the step call site instead of internal actions, enhancing error reporting clarity.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at e4fbc1d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago

README badge

README badge for corey-alix/dwp-hours/playwright-testing-assistant