> Not all of the tests, necessarily, but enough to set an example, set the standard, and get the ball rolling. I think you stopped your quote too soon. Writing

> Not all of the tests, necessarily, but enough to set an example, set the standard, and get the ball rolling. I think you stopped your quote too soon. Writing a couple tests sets a pattern, an example o follow, and demonstrates how important they are because you are willing to take time to do them to begin with. But just giving lip service to the importance of them does not change a culture of untested code. Setting up code coverage reports, test harnesses, a few examples, and then talking about the test metrics shows it's important to management.