---
name: playwright-testing-assistant
description: Provides guidance for implementing end-to-end tests using Playwright, following best practices for test structure, reliability, and maintainability.
title: playwright-testing-assistant
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/playwright-testing-assistant
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/playwright-testing-assistant`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/playwright-testing-assistant`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/playwright-testing-assistant) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/playwright-testing-assistant`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/playwright-testing-assistant --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/playwright-testing-assistant --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.
