Cheesecan wrote:Unit testing can only detect so much. Usually you would complement unit testing by doing dynamic user tests based on use cases(playing the game in different ways). If you don't want to be a tester indirectly, spring is probably not for you.
I'm a developer myself, but not in C++, one who can take (even badly worded) criticism better than (some of) the spring developers.
And i'm no fan of unit testing, it adds a lot of work the development cycle, much like premature documenting does.
I'm merely asking/telling the spring developers to test their changes themselves with RAI and BA/TA when changing something in the core code, and thus before forcing a potentially crippling change upon the entire end-user community.
Contrary to fullfledged unit-testing, it would be trivially simple for them, really.
All they have to do is start it up, and check every 15 or 30 minutes for things like CPU rape, crashes/freezes.