symfony:functional-tests
Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback
Savant verdict: Pending analysis
Imported from the source hub; Savant's analysis is still running.
Live evaluation
Not evaluated yet. Workspaces can request a live evaluation.
Security assessment
Scan pending.
Structure
- No license declaredConfirm you may reuse this skill before importing it into your repository.
SKILL.md
--- name: symfony:functional-tests allowed-tools: - Read - Write - Edit - Bash - Glob - Grep description: Write functional tests for Symfony controllers and HTTP endpoints using WebTestCase, getContainer, loginUser, and DAMA rollback --- # 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. 3. Refactor while preserving green suite. 4. 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`