home / skills / makfly / superpowers-symfony / e2e-panther-playwright

e2e-panther-playwright skill

safe

This skill helps you drive deterministic end-to-end tests for Symfony with Panther and Playwright, ensuring regression protection across components.

npx playbooks add skill makfly/superpowers-symfony --skill e2e-panther-playwright

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.1 KB

---

name: symfony:e2e-panther-playwright
allowed-tools:
  - Read
  - Glob
  - Grep
description: Drive Symfony delivery with deterministic tests and strong regression protection. Use for e2e panther playwright tasks.
---

# E2e Panther Playwright (Symfony)

## Use when
- Building regression-safe behavior with TDD/functional/e2e tests.
- Converting bug reports into executable failing tests.

## Default workflow
1. Write failing test for target behavior and one boundary case.
2. Implement minimal code to pass.
2. Refactor while preserving green suite.
2. Broaden coverage for invalid/unauthorized/not-found paths.

## Guardrails
- Prefer deterministic fixtures/builders.
- Assert observable behavior, not internal implementation.
- Keep tests isolated and stable in CI.

## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.

## Output contract
- RED/GREEN/REFACTOR trace.
- Test files changed and executed commands.
- Coverage and confidence notes.

## References
- `reference.md`
- `docs/complexity-tiers.md`

Overview

This skill drives Symfony end-to-end testing using Panther and Playwright to create deterministic, regression-safe delivery. It focuses on a TDD-style RED/GREEN/REFACTOR loop to convert bugs into executable tests and protect behavior across releases. The skill reports changed test files, executed commands, and coverage/confidence notes.

How this skill works

You write a failing e2e test that captures the target behavior and at least one boundary case, then implement the minimal change to make the test pass and refactor while keeping the suite green. The tool emphasizes deterministic fixtures and isolated tests, running Panther and Playwright tasks to exercise the full stack and capture observable outcomes. Outputs include the RED→GREEN→REFACTOR trace, which files changed, the commands run, and short notes on coverage and confidence.

When to use it

When you want regression-safe behavior delivery with TDD or functional/e2e tests
When converting a bug report into an executable failing test before fixing
When adding critical user flows that must remain stable in CI
When validating authorization, not-found, and invalid-input paths in production-like scenarios

Best practices

Start with a failing test and include at least one boundary case
Use deterministic fixtures and builders to avoid flaky runs
Assert observable behavior (HTTP responses, UI state), not internal implementation
Keep tests isolated and lightweight so they are stable in CI
Broaden coverage gradually: invalid, unauthorized, and not-found cases after green

Example use cases

Turn a reported UI bug into a failing Panther/Playwright test, fix the code, and prove the regression is gone
Add end-to-end coverage for a payment or signup flow with deterministic user builders
Protect critical admin flows by adding authorization and not-found test cases
Use RED/GREEN/REFACTOR trace to document the change set and commands executed for a release audit

FAQ

What does the output include?

A RED→GREEN→REFACTOR trace, list of test files changed, executed commands, and short coverage/confidence notes.

How do you avoid flaky tests?

Use deterministic fixtures/builders, isolate tests, assert on observable behavior, and keep setup minimal to reduce timing and environment variance.