Am 12.01.2015 um 23:56 schrieb Adrien Destugues:
Writing tests that are never run by anyone is even less motivating. It's also not an excuse: I did the changes and did my best to test them with the available tools (which is not much: I can only check that the code builds, and the resulting system boots on my machine). If this is not enough to keep everyone confident that the code works, it's not because it is a bad time to do the change, but because we need better testing tools, and better tests.
All Oliver said is that you should write tests when they are missing.That there is no automatic service that runs the test suite for you is not ideal, but it's not an excuse not to run those tests yourself.
The better the test suite, the higher the motivation and pressure to make it part of our build infrastructure :-)