[TYPO3-core] RFC: Blueprint standalone unit tests

Helmut Hummel helmut.hummel at typo3.org
Mon Oct 14 16:46:05 CEST 2013

Hi Olly,

On 14.10.13 11:55, Oliver Hader wrote:

> Anyway, I'd like to know, whether and how this affects extension authors
> or whether this plan is just releated to core development.

Extension authors are not affected at all by this but they can benefit 
from this change.

> Are there other possible risks/drawbacks in terms of performance (test
> take longer to be executed)

If anything, tests will become faster.

> or the complexity in writing tests for a
> correct mocking?

Tests with incomplete mocking are broken tests you don't know about 
because they do not fail at first sight. But they will give you false 
positives very often when changing code in other areas.

So yes, it might be more complicated to write properly mocked tests, but 
it will be easier in the future as the tests are more stable, but the 
overhead should be very low, if not none for certain areas.

> If there are none, the "risks" section in the
> blue-print should be filled with "none"

I would rather change that to none.

> and the current "Code
> encapsulation and overall quality may improve" should be part of the
> motivation then.

Good point.

Kind regards,

Helmut Hummel
Release Manager TYPO3 6.0
TYPO3 Core Developer, TYPO3 Security Team Member

TYPO3 .... inspiring people to share!
Get involved: typo3.org

More information about the TYPO3-team-core mailing list