[TYPO3-core] RFC: Blueprint standalone unit tests

Oliver Hader oliver.hader at typo3.org
Mon Oct 14 11:55:29 CEST 2013

Hi Christian,

thanks for handing in this blue-print to describe the changes for this
task. The "risk" section there sounds a bit sarcastic, but I guess that
is intended... ;-)

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

Are there other possible risks/drawbacks in terms of performance (test
take longer to be executed) or the complexity in writing tests for a
correct mocking? If there are none, the "risks" section in the
blue-print should be filled with "none" and the current "Code
encapsulation and overall quality may improve" should be part of the
motivation then.

Thanks & I'm looking forward to more feedback on that.


Am 13.10.13 22:09, schrieb Christian Kuhn:
> Hey,
> it would be great to have your comments on the blueprint "Standalone
> Unit Tests" [1] to further consolidate the future goals and path of unit
> test development with TYPO3 CMS.
> Regards
> Christian
> [1] http://wiki.typo3.org/Blueprints/StandaloneUnitTests

Oliver Hader
TYPO3 CMS Core Team Leader

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

More information about the TYPO3-team-core mailing list