sbuerk/typo3-cmscomposerinstallers-testingframework-bridge

Compatibility patch for extension testing with TYPO3 v12

Maintainers

👁 sbuerk

Package info

github.com/sbuerk/typo3-cmscomposerinstallers-testingframework-bridge

Type:composer-plugin

pkg:composer/sbuerk/typo3-cmscomposerinstallers-testingframework-bridge

Statistics

Installs: 50 780

Dependents: 16

Suggesters: 0

Stars: 5

Open Issues: 1

0.1.3 2023-04-11 13:28 UTC

Requires

  • php: ^7.4 || ^8.0 || ^8.1 || ^8.2
  • composer-plugin-api: ^2.0.0

Suggests

None

Provides

None

Conflicts

None

Replaces

None

GPL-2.0-or-later dadf2835b10115574e0e66dc4f0d1b6dd5c5a191

  • Stefan Bürk <stefan.woop@buerk.tech>

This package is auto-updated.

Last update: 2026-05-28 21:07:38 UTC


README

Mission

This composer plugin has the intermediate mission to keep extension development testing against TYPO3 v12 working, which recently added enforced CMS Composer Installers 5. This breaks the way testing works.

Until proper overwork of the whole testing infrastructure is done, this plugin provides proper symlinked TYPO3 system extension and the extension to the known "legacy paths". Thus, Unit-, Functional and Acceptance testing works as before without any changes in extensions which already tests against TYPO3 v12. This also helps when using typo3/cms-composer-installers:4.0.0-RC1 with v11.

Starting with 0.1.x of this composer plugin project level testing is also supported.

⚠️ This is an unofficial intermediate workaround, which may vanish anytime.

Installation and usage

This plugin should be only added as development dependency, so it get not shipped and installed on installation in a instance.

composer require --dev sbuerk/typo3-cmscomposerinstallers-testingframework-bridge

The plugin uses already provided information and configuration from composer and the CMS Composer Installers, thus no configuration needed for this plugin.