Symfony:functional Tests Skill
- 439 installs
- 190 repo stars
- Updated August 6, 2026
- makfly/superpowers-symfony
symfony:functional-tests is a Claude Code skill that writes Symfony WebTestCase HTTP functional tests exercising routes, controllers, forms, and request-response flows with DAMA database rollback.
About
symfony:functional-tests is a testing skill in MakFly's superpowers-symfony plugin (44 skills total) for Symfony 7.4 LTS and 8.x projects. It follows a RED-GREEN-REFACTOR workflow: write a failing test for target behavior plus one boundary case, implement minimal passing code, refactor while green, then broaden coverage for invalid, unauthorized, and not-found paths. The skill uses Symfony WebTestCase with getContainer, loginUser for authenticated routes, and DAMA DoctrineTestBundle rollback to keep database tests isolated in CI. Guardrails favor deterministic fixtures, observable behavior assertions over internals, and stable isolated tests. Developers reach for symfony:functional-tests before release when HTTP endpoints, controller logic, and form submissions need regression-safe coverage beyond unit tests.
- HTTP client and BrowserKit-style flows
- Route and controller integration coverage
- Form submission and redirect assertions
- Database fixture and transaction patterns
- CI-ready Symfony test kernel setup
Symfony:Functional Tests by the numbers
- 439 all-time installs (skills.sh)
- Ranked #642 of 2,189 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
npx skills add https://github.com/makfly/superpowers-symfony --skill symfonyfunctional-testsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 439 |
|---|---|
| repo stars | ★ 190 |
| Last updated | August 6, 2026 |
| Repository | makfly/superpowers-symfony ↗ |
How do you write Symfony functional HTTP tests?
Write Symfony HTTP kernel functional tests that exercise routes, controllers, forms, and full request-response flows before release.
Who is it for?
Symfony engineers adding HTTP regression tests for controllers, routes, and forms who want WebTestCase patterns with database rollback isolation.
Skip if: Teams needing only PHPUnit unit tests without HTTP kernel boot, or full browser E2E, should use test-doubles-mocking or e2e-panther-playwright instead.
When should I use this skill?
The developer asks for Symfony functional tests, WebTestCase examples, HTTP endpoint regression tests, or DAMA rollback setup before release.
What you get
WebTestCase test classes, RED-GREEN-REFACTOR trace, executed test commands, and coverage notes for HTTP endpoints
- WebTestCase test files
- Executed test command output
- RED-GREEN-REFACTOR trace with coverage notes
By the numbers
- One of 44 skills in the superpowers-symfony Claude Code plugin
- Default workflow includes 4 RED-GREEN-REFACTOR steps plus edge-case broadening
Files
Functional Tests (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.mddocs/complexity-tiers.md
Functional Tests Reference (Symfony)
Use this reference for implementation details and review criteria specific to functional-tests.
Skill Operating Checklist
Design checklist
- Confirm operation boundaries and invariants first.
- Minimize scope while preserving contract correctness.
- Test both happy path and negative path behavior.
Validation commands
- ./vendor/bin/phpunit --filter=...
- ./vendor/bin/phpunit
- ./vendor/bin/pest --filter=...
Failure modes to test
- Invalid payload or forbidden actor.
- Boundary values / not-found cases.
- Retry or partial-failure behavior for async flows.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.623k210kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.193k210k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.191k269k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.128k167k
Prisma PostgresQuickly inspect data, view metrics, link existing Postgres instances, and retrieve connection strings without switching between CLI, Studio, and the web console.126k50
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.112k12.4kHow it compares
Pick symfony:functional-tests over tdd-with-pest when the goal is full HTTP kernel route and controller coverage—not isolated unit-level TDD cycles.
FAQ
What test base class does symfony:functional-tests use?
symfony:functional-tests uses Symfony WebTestCase to boot the HTTP kernel, exercise routes and controllers through real request-response cycles, and access services via getContainer.
How does symfony:functional-tests keep database tests isolated?
symfony:functional-tests relies on DAMA DoctrineTestBundle rollback so each functional test runs in a transaction that rolls back, keeping CI database state clean without manual cleanup.
What workflow does symfony:functional-tests follow?
symfony:functional-tests applies RED-GREEN-REFACTOR: write a failing test and one boundary case, implement minimal passing code, refactor while green, then add invalid, unauthorized, and not-found coverage.