On 4 December 2012 12:57, Sven Van Caekenberghe <sven@stfx.eu> wrote:
But I think we do agree ;-)
What makes me value tests a bit above documentation (but not so much that I am saying that documentation is not important), are two things:
- tests are machine enforceable/controllable - you can find them exactly using senders or references
well, a test is more direct and concise way of telling how your stuff works (or should work), as well as serving as a source of example. what you write in a test, could take like 10 times more explaining same in docs. still. with tests you cannot tell: - why it is done like that - what are responsibilities of components and how you can change/replace them if needed. - what is best/recommended practices to use your software - where the starting/entry point. -- Best regards, Igor Stasenko.