Contains scripts to test and release TYPO3 Extensions

v10.3.0 2022-03-22 23:48 UTC

This package is auto-updated.

Last update: 2024-07-09 23:31:39 UTC


Test your TYPO3 Extensions with the utilities provided by the TYPO3 core using:

  • the typo3/testing-framework package
  • docker and docker-compose
  • the typo3gmbh/php* docker images

Hint 1: currently each version of the tools only supports one TYPO3 core version.

Hint 2: currently the Composer dependencies must be installed in the .Build directory. See doc/composer-sample.json for the needed configuration.


Edit composer.json

Adjust the settings in your composer.json file as described in doc/composer-sample.json.

After that run composer update.

Require dynamically

If you want to test multiple core versions you can require different versions of the buildtools dynamically during your build process.

For TYPO3 10:

composer require --dev de-swebhosting/typo3-extension-buildtools:dev-master

For TYPO3 9:

composer require --dev de-swebhosting/typo3-extension-buildtools:dev-TYPO3_9

Run locally

Before you can execute a script locally, you need to set your Extension key as an environment variable:

export TYPO3_EXTENSION_KEY="<my_extension_key>"

After that you can run the different commands.

  • - For running Unit, Functional and Acceptance tests
  • - For checking / fixing PHP code style via PHP_CodeSniffer
  • - Prepare docs and ext_emconf.php for a release
  • - Upload Extension to TER

Run in travis

Have a look at the doc/travis-sample.yml file. You need to

  1. replace <your_extension_key> with the Extension key of your extension
  2. remove [your_custom_codestyle] or replace it with the name of the ruleset you want to use for the code style checker (see Code style checking).

The Example Travis CI config will

  • validate the composer.json file
  • check the code style of your PHP code
  • run Unit Tests for PHP 7.3 and 7.4
  • run functional Tests for PHP 7.3 and 7.4
  • run PHP linting for PHP 7.3 and 7.4
  • run acceptance tests for PHP 7.3 and 7.4

It will also try to deploy your Extension to TER when a tag is pushed. You need to set your TYPO3 login data in Travis environment variables for this to work (see Deploy to TER).


Write tests

Unit test

To write a unit test create the folder Tests/Unit in your Extension and add your first test case by extending TYPO3\TestingFramework\Core\Unit\UnitTestCase:

namespace Vendor\MyExt\Tests\Unit;

use TYPO3\TestingFramework\Core\Unit\UnitTestCase;

class MyFirstUnitTest extends UnitTestCase {

Functional test

To write a functional test create the folder Tests/Functional in your Extension and add your first functional test case by extending TYPO3\TestingFramework\Core\Functional\FunctionalTestCase:

namespace Vendor\MyExt\Tests\Functional;

use TYPO3\TestingFramework\Core\Functional\FunctionalTestCase;

class MyFirstFunctionalTest extends FunctionalTestCase {

Execute tests

For executing Unit tests, run this command:

.Build/bin/ -s unit -p "<PHP version>"

For executing functional tests, run this command:

.Build/bin/ -s functional -d "<database type>" -p "<PHP version>"

<database type> can be:

  • mariadb
  • mssql
  • postgres
  • sqlite

Acceptance testing


You can find some boilerplate code for acceptance testing in the doc/acceptance folder.

Copy the codeception.yml file into your Extension's Tests folder and

adjust the configured namespace.

The frontend subfolder contains a skeletton for creating a Frontend test suite.

Copy all files and folders from this directory to the Tests/Acceptance folder of your Extension and adjust

the namespaces in all files.

After that you should be able to run your first acceptance test (located in the Frontend subdirectory).

.Build/bin/ -s acceptance -a Frontend


The setup for Backend acceptance testing is quite similar to the Frontend.

Copy the contents of the backend folder into the Tests/Acceptance folder of your Extension and you are good to go.

The acceptance test command executes the Backend testsuite by default:

.Build/bin/ -s acceptance


Add these to the config of the web service in the docker-compose.yml to temporarily enable Development context for better debug output in the Frontend and the possibility to access the webserver from your local machine

Important! For this to work you need to add the --service-ports flat to the docker-compose command

in The final command looks like this:

docker-compose run --service-ports acceptance_backend_mariadb10

This config needs to be added to the docker-compose.yml file:

      - "8000:8000"
      TYPO3_CONTEXT: Development

Code style checking

To execute code style checks, you can use this command:


It checks all known locations of PHP files in TYPO3 Extensions with some default configuration based on the TYPO3 core coding guidelines.

You can adjust the ruleset, by adding Tests/CodeSniffer/MyCodingStandard/ruleset.xml to your Extension.

This is an example to use the default rules and disable line length checking for TCA configuration files:

<?xml version="1.0"?>
<ruleset name="MyCodingStandard">
	<description>Based on PSRDefault. Adjust only if REALLY neccessary!</description>
	<rule ref="PSRDefault"/>
	<rule ref="Generic.Files.LineLength">

After you created the ruleset, you must provide its name to the code style checker:

.Build/bin/ MyCodingStandard

To automatically fix code style errors, you can pass the fix keyword as first parameter:

.Build/bin/ fix [MyCodingStandard]

Deploy to TER

Use the script, to prepare a release:

bash .Build/bin/ "<semantic_version>"

This will set the provided version number in ext_emconf.php and Documentation/Settings.cfg and create a new release using the git flow release commands.

After that you can push all branches and tags. The pushed tag will be published to TER.

git push && git push --tags && git checkout develop && git push


This work is based on the TYPO3 testing framework and the awesome documentation at