typo3-testing

Create and configure TYPO3 extension tests with PHPUnit and CI/CD integration.

51|13|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/netresearch/claude-code-marketplace --skill typo3-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typo3-testing
Source: https://github.com/netresearch/claude-code-marketplace/tree/main/skills/typo3-testing
Command: npx skills add https://github.com/netresearch/claude-code-marketplace --skill typo3-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typo3/testing-framework, phpunit/phpunit, codeception/codeception, codeception/module-webdriver, phpstan/phpstan, phpstan/phpstan-strict-rules, saschaegerer/phpstan-typo3, rector/rector, ssch/typo3-rector, friendsofphp/php-cs-fixer, overtrue/phplint, docker, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Setting up and maintaining robust testing for TYPO3 extensions can be complex and time-consuming, often leading to inconsistent quality or skipped tests. This skill automates the entire testing lifecycle, from infrastructure setup to CI/CD integration, ensuring high-quality, reliable TYPO3 extensions with minimal effort.

Core Features & Use Cases

  • Automated Test Setup: Quickly generate Unit, Functional, and Acceptance tests with pre-configured PHPUnit and Codeception.
  • CI/CD Integration: Seamlessly integrate testing into GitHub Actions or GitLab CI pipelines for continuous quality assurance.
  • Quality Tooling: Enforce code standards with PHPStan, Rector, and php-cs-fixer, catching bugs and improving code health automatically.
  • Use Case: A TYPO3 developer needs to add a new feature to an extension. They can use this skill to instantly generate a functional test, set up the necessary database fixtures, and ensure it passes all quality checks before deployment, all with a few commands.

Quick Start

Set up the testing infrastructure for my TYPO3 extension, including unit and functional tests.

Frequently Asked Questions about typo3-testing

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

FAQPage Schema
How do I set up automated testing for a TYPO3 extension?

Automated testing for TYPO3 extensions involves configuring PHPUnit for unit and functional tests, then integrating them into CI/CD pipelines like GitHub Actions or GitLab CI. This Skill provides pre-configured templates, scripts, and infrastructure setup to generate tests, manage fixtures, and enforce code quality checks automatically across your extension.

Can I use PHPStan and Rector with TYPO3 extensions?

Yes. PHPStan with TYPO3-specific rules and Rector for automated code refactoring are fully integrated into this Skill's quality tooling. They catch bugs, enforce coding standards, and ensure compatibility with TYPO3 v12 and v13 while maintaining consistent code health across your extension.

What's the best way to set up CI/CD for TYPO3 extension testing?

This Skill automates CI/CD integration by providing ready-to-use configurations for GitHub Actions and GitLab CI that run unit, functional, and E2E tests on every commit. It handles PHPUnit setup, quality checks with PHPStan and php-cs-fixer, and generates test infrastructure so your extension passes all quality gates before deployment.

How do I create functional and acceptance tests for TYPO3?

Functional and acceptance tests for TYPO3 are generated using PHPUnit and Codeception with pre-configured fixtures and database setup. This Skill provides templates and automation scripts that handle test generation, WebDriver-based E2E testing, and Playwright accessibility testing so you can focus on test logic rather than infrastructure.

Do I need Docker to run TYPO3 extension tests?

Docker is listed as a supported dependency for containerized test environments, but this Skill's testing framework works with local PHPUnit and Codeception setups. Docker enables isolated, reproducible test environments; the Skill provides flexibility to run tests locally or in containers depending on your CI/CD pipeline.

Why should I use mutation testing with PHPUnit for TYPO3?

Mutation testing with Infection validates that your test suite actually catches bugs by introducing code mutations and verifying tests fail. This Skill integrates Infection to ensure your TYPO3 extension tests have sufficient coverage quality, not just line coverage, improving confidence in code reliability before release.