git:20260816.6f2515e to git:20260917.36aca93

21 added, 1 removed. Audit A to A.

---

name: typo3-testing

- description: "Use when setting up TYPO3 extension test infrastructure, writing unit/functional/E2E tests, configuring PHPUnit 11/12/13, mutation testing, mocking final classes (v14), CI/CD matrix across TYPO3 12/13/14.3 LTS, dev-dependency consolidation via typo3-ci-workflows meta-package, or debugging CI failures. Also triggers on: testing-framework setup, ensure proper testing, test matrix, integration testing, e2e testing, coverage, test generation."

+ description: "Use when a reported defect has to be reproduced as a failing test before it is fixed, when a change to a template or to any rendered output has to be proved, or when setting up TYPO3 extension test infrastructure, writing unit/functional/E2E tests, configuring PHPUnit 11/12/13, mutation testing, mocking final classes (v14), CI/CD matrix across TYPO3 12/13/14.3 LTS, dev-dependency consolidation via typo3-ci-workflows meta-package, or debugging CI failures. Also triggers on: testing-framework setup, ensure proper testing, test matrix, integration testing, e2e testing, coverage, test generation."

---

# TYPO3 Testing Skill

+ ## A Report Becomes a Failing Test Before It Becomes a Fix

+ A bug report is a test that does not exist yet. Write it from the report's own

+ input and expected output, run it, and see it fail for the reason the report

+ gives. A test written after the fix proves only that the code does what it

+ does.

+ **Output produced through a template is not covered by a unit suite.** The unit

+ suite loads PHP classes and never renders a Fluid template, so an edit to a

+ template leaves the suite green while the page is broken. Prove such a change by

+ rendering it: a functional test that calls the rendering path and asserts the

+ rendered string.

+ Read the rendered string, not the exit code. Fluid does not raise on an inline

+ expression it cannot parse -- it emits the expression verbatim, so the markup

+ reaches the browser with `{f:if(...)}` sitting inside the attribute it was

+ written into, and a test asserting only that nothing threw will pass. When an

+ inline expression would nest one call inside another, write it as a tag

+ (`<f:if>`) or compute the value in PHP and pass it in.

## Assessment-First Rule

**When enhancing an existing test suite** (not from scratch), run FIRST:

```bash

automated-assessment typo3-testing

```

> Install `typo3-conformance` and `enterprise-readiness` for broader coverage.

Generates a gap report from 73+ checkpoints (PHPUnit, PHPStan, runTests.sh, architecture, mutation, CI matrix, coverage).

**Use the report as the task list.** Resolve mechanical failures before manual test writing.

### Applies

- "enhance/improve/strengthen tests", "increase coverage/mutation"

- "enterprise grade", "A+ testing"

### Does NOT Apply

- From scratch, writing a specific test, debugging a failure

---

## 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, 70%+ coverage | CI/Release |

## runTests.sh - Mandatory

`Build/Scripts/runTests.sh` is mandatory: executable, with `-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` (see `references/captainhook-setup.md`).

## Commands

```bash

# 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)

```

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/`, `.md` implied)

### 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 tests, `Environment::initialize`, `NormalizedParams` TypeError, `backupGlobals` → `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`

- Backend module 500 / wrong ViewHelper namespace / runaway canvas → `backend-module-render-verification.md`

- Non-admin BE-user access enforcement → `backend-user-access-testing.md`

- Package will not install next to TYPO3 → `framework-compat-gate.md`

## Links

[TYPO3 Testing Docs](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/Testing/) |

[Tea Extension](https://github.com/TYPO3BestPractices/tea) |

[phpat](https://github.com/carlosas/phpat) |

[Infection](https://infection.github.io/)