Maybe not so related to the story, but anyway:

Game developers typically use C or C++ (at least the ones that create processing heavy 3D games), and it doesn't help that the open source frameworks for unit testing in C++ are not too great. The problem is that there are about 40 of them (see http://en.wikipedia.org/wiki/List_of_unit_testing_frameworks#C.2B.2B), many developers spreading their talent over their own creation instead of working together on something good. We use UnitTest++ at work, and it hurts to see that the mailinglist is about dead, with interesting proposals getting no answer, and no updates since 2008. GTest seems better, but we can't switch just like that.

Contrast this to Java, where you basically have JUnit and TestNG in healthy competition.

There are commercial options, like UquoniTest (see http://www.q-mentum.com/uquonitest.php) which has great features, but I'd rather wait until they're compatible with UnitTest++ (as they promise on their blog), and Cantata++ (see http://www.ipl.com/products/tools/pt400.uk.php) which has code coverage.

Actually, in 2 billion years the moon will have moved away from the earth far enough that it can no longer stabilize the earths rotation axis. This will cause the axis to move much more than it does today, so it may from time to time point to the sun, continually heating up one half to death and letting the other half freeze to death.

So by then there will already be no more life on earth. Unless we can capture the moon with a lasso by that time.