#110063composer dependency of fixture extension as requirement to actual extension to test is removed
Description
I have one extension which I want to test.
This extension has a fixture extension with a dependency to the actual extension to test. That’s because order matters (e.g. Services Files, ext_* files, TCA, etc.).
Since 14.2 this requirement is ignored in TYPO3\CMS\Core\Package\Package->ignoreDependencyInPackageConstraint() as the extension under test is known by composer and therefore ignored …
I don’t understand the reason and therefore am unable to fully cover the extension with automated tests anymore.
Looks like it got introduced with https://git.typo3.org/typo3/typo3/-/commit/15c263485c474ba9caf13b71588e5391179697c8 based on #108345 and #96388.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 2
-
Helmut Hummel commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-09-14T20:24:35+00:00" > 09/14/26, 20:24 </span> -
Daniel Siepmann commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-10-19T05:10:56+00:00" > 10/19/26, 05:10 </span>I implemented a workaround. So I’m fine with closing the issue, as it seems I’m the only one having the issue.
please provide more detailed information on how to reproduce. Like composer.json of the extension and fixture extensions, exact way the tests are performed, etc.