[TYPO3-core] RFC: Blueprint standalone unit tests

Christian Kuhn lolli at schwarzbu.ch
Mon Oct 14 20:25:23 CEST 2013


Thx for feedback. I adapted the blueprint a bit to reflect it.

On 10/14/2013 04:46 PM, Helmut Hummel 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.

Yes. A good example is ext:news, Georg had to go through quite some 
steps to run the tests on travis-ci.org. This will be simplified.

>> 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.

Yes. I've already lost quite some time hunting cross-dependencies 
between tests. This will be improved if the encapsulation is better.


More information about the TYPO3-team-core mailing list