TYPO3 Core

You are right, there's some relationship between the T3Cache test class and the problem I've described.

But the real problem seems to be that this file is added to the typo3temp/autoload/autoload_classmap.php and loaded at all. Until 7.3, only the relevant files from our Aimeos extensions (listed in their composer.json file, not test files) were loaded by our custom autoloader.

If we remove it, we can't test the extension on travis-ci any more. How can we solve this?

Aimeos no-lastname-given wrote:

If we remove it, we can't test the extension on travis-ci any more. How can we solve this?

for the time being, use a different (non conflicting) namespace for your test class

That doesn't work because in order to enforce the interface for the constructor parameter it must be of type \TYPO3\CMS\Core\Cache\Frontend\FrontendInterface.

We've also thought about encapsulating the test class and the emtpy interface into a "if" condition and load the class only if it's not loaded before but then it will depend on if the real class is really loaded first. This might lead to even harder to detect errors :-(

Aimeos no-lastname-given wrote:

That doesn't work because in order to enforce the interface for the constructor parameter it must be of type \TYPO3\CMS\Core\Cache\Frontend\FrontendInterface.

We've also thought about encapsulating the test class and the emtpy interface into a "if" condition and load the class only if it's not loaded before but then it will depend on if the real class is really loaded first. This might lead to even harder to detect errors :-(

Where can I have a look at the code of the extension and what is the exact location of that file?

You can btw. create classes with eval instead of including files.

Anyway, we may be able to fix this, if you provide additional information.

Aimeos no-lastname-given wrote:

That doesn't work because in order to enforce the interface for the constructor parameter it must be of type \TYPO3\CMS\Core\Cache\Frontend\FrontendInterface.

Well. Thinking about that again: what exactly do you mean?

Just create a mock from the plain (existing interface) and you should be fine. you don't need the fixture you created at all

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40966

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40966

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40966