typo3-testing
TYPO3 Testing Skill
Assessment-First Rule
When enhancing an existing test suite (not setting up from scratch), run FIRST:
automated-assessment typo3-testing
Install additional skills (e.g.
typo3-conformance,enterprise-readiness) for broader assessment coverage.
This generates a gap report from 73+ checkpoints covering PHPUnit config, PHPStan level, runTests.sh, CaptainHook hooks, architecture tests, mutation thresholds, CI matrix, and coverage per class.
Use the assessment report as the task list. Resolve mechanical checkpoint failures before manual test writing.
When This Rule Applies
- "enhance/improve/strengthen tests", "increase coverage/mutation score"
- "enterprise grade", "A+ testing", "fix all findings"
When This Rule Does NOT Apply
- Setting up from scratch, writing a specific test, debugging a failing test
References for TYPO3 extension testing.
Test Type Selection
| Type | Use When | Speed |
|---|---|---|
| Unit | Pure logic, no DB, validators, utilities | Fast |
| Functional | DB interactions, repositories, controllers | Medium |
| Architecture | Layer constraints, dependency rules (phpat) | Fast |
| E2E (Playwright) | User workflows, browser, accessibility | Slow |
| Integration | HTTP client, API mocking, OAuth flows | Medium |
| Mutation | Test quality verification, 70%+ coverage | CI/Release |
runTests.sh - Mandatory
Build/Scripts/runTests.sh is mandatory. Must be executable, support -s (suite) and -p (PHP version).
Git Hooks
Netresearch default: Build/captainhook.json (declared in composer.json extra.captainhook.config). Verify: ls Build/captainhook.json .git/hooks/pre-commit 2>/dev/null (see references/captainhook-setup.md).
Commands
# Setup (from skill dir)
scripts/setup-testing.sh [--with-e2e]
scripts/validate-setup.sh
scripts/generate-test.sh <Type> <Class>
# Run (always via runTests.sh)
Build/Scripts/runTests.sh -s unit|functional|phpstan|cgl|mutation|ci
Verify tests fail before fix, pass after. Bug fixes use the strict TDD loop in references/tdd-discipline.md — no "tested/verified" claims without pasted output.
Scoring Requirements
Unit tests required (70%+ coverage). Functional tests required for DB operations. phpat required for architecture points. PHPStan level 10.
References (in references/)
unit-testing.md | functional-testing.md | functional-test-patterns.md | integration-testing.md | e2e-testing.md | accessibility-testing.md | ddev-testing.md | test-runners.md | architecture-testing.md | ci-debugging.md | ci-cd.md | quality-tools.md | mutation-testing.md | fuzz-testing.md | performance-testing.md | typo3-v14-final-classes.md | mock-validity.md | javascript-testing.md | captainhook-setup.md | enforcement-rules.md | event-dispatch-testing.md | crypto-testing.md | test-environment-guards.md | sonarcloud.md | typo3-ci-config-patterns.md | tdd-discipline.md | ci-workflows-meta-package.md | synthetic-secret-fixtures.md | release-workflow-validation.md
Content Triggers
- CI failures across TYPO3 versions →
ci-debugging.md - Functional tests with TSFE context →
functional-testing.md - Mock failures across dependency versions →
mock-validity.md - Image/extension-dependent tests →
test-environment-guards.md - Event dispatcher testing with try/catch →
event-dispatch-testing.md - Meta-package, typo3-ci-workflows, no-plugins →
ci-workflows-meta-package.md - Fake secrets, push-protection, cs-fixer concat →
synthetic-secret-fixtures.md - Burned tag, validate before tagging →
release-workflow-validation.md