symfony:functional-tests

Convert Symfony bug reports into executable failing functional tests.

187|17|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/MakFly/superpowers-symfony --skill symfony-functional-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symfony:functional-tests
Source: https://github.com/MakFly/superpowers-symfony/tree/main/skills/functional-tests
Command: npx skills add https://github.com/MakFly/superpowers-symfony --skill symfony-functional-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure your Symfony application's behavior is robust and protected against regressions by driving development with deterministic tests.

Core Features & Use Cases

  • TDD/BDD Workflow: Implement the RED-GREEN-REFACTOR cycle for functional and end-to-end tests.
  • Regression Protection: Convert bug reports into executable failing tests to prevent recurrence.
  • Use Case: When a bug is reported, use this skill to write a failing test that reproduces the bug, then implement the fix and refactor, ensuring the bug stays fixed.

Quick Start

Use the symfony:functional-tests skill to drive the development of a new feature with TDD.

Frequently Asked Questions about symfony:functional-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write functional tests in Symfony to reproduce a reported bug?

You drive Symfony functional tests by converting a bug report into an executable failing test that reproduces the error. This establishes regression protection before you implement the actual bug fix.

What is the RED-GREEN-REFACTOR cycle for Symfony functional tests?

The RED-GREEN-REFACTOR cycle for Symfony functional tests is a TDD workflow where you first write a failing test (RED), implement the code to make it pass (GREEN), and then clean up the code without changing behavior (REFACTOR).

How do you ensure deterministic end-to-end tests in a Symfony application?

Deterministic end-to-end tests in a Symfony application require strict adherence to guardrails for fixture management and asserting only observable behavior, preventing flaky test results and ensuring reliable regression protection.

Can I use TDD for Symfony regression testing when adding new features?

Yes, you can use TDD for Symfony regression testing when adding new features. The workflow drives application delivery by writing deterministic functional tests first, ensuring new code does not break existing behavior.

What are the limitations of using functional tests for PHP regression protection?

The primary limitation is that functional tests require strict fixture management and must assert only observable behavior to remain deterministic. Without adhering to these guardrails, tests become flaky and fail to provide reliable regression protection.