[TYPO3-team-core-v5] Current sloppy way of handling tests and changes

[Karsten Dambekalns]

Hi.

I understand the drive to put things into master and I also understand the feeling that things need to keep going.

At the same time simply saying "we'll fix the tests after T3BOARD" doesn't help anyone. First of all, failing unit tests will stop any updates to the submodule pointers in the distribution(s). Second, if we get used to failing tests (as opposed to failing builds[1]), we are already on the road to hell. Or something.

Worst of all, if we could tolerate a failing test, we should *never* tolerate a test that fails with a fatal error. There are at least two of those currently, when applying the property mapper changes. Even with the huge new operator and persistence changes we managed to keep that cleaner and greener.

All, in all, one step slower might give us faster results in the end...

Regards,
Karsten

[1] Currently the commit builds fail in post-testing when collecting code coverage. It works fine here, but even updating PHPUnit and friends on Inspire did not help so far. But note the difference between a failing test and a failing build...
-- 
Karsten Dambekalns
Gimme Five!
http://typo3.org/gimmefive