You don't usually see people (including me!) talk about their mistakes openly. But I think it is good to think about the mistakes we made in the past, so that we don't commit the same errors in the future.
Does your organisation develop software in house? Are you responsible for testing applications? Are you a tester of applications? If so, where do you get your test data? You know, the data you put in the databases that allow you to test the applications, where does it come from?
Phil Haack told some of his pains in dealing with unit testing in the post Tell Me Your Unit Testing Pains. Here I would like to share some experience of my own.
Teams constrained by resources are always looking for a competitive advantage in reducing costs and improving software quality. This advantage can be achieved by implementing two best practices:
For developers familiar with unit tests, being able to get the immediate feedback from the tests is a great boost to the morale. The experience of writing tests (regardless of whether the tests are written first or last) is so rewarding that one naturally want to do it for every layer of the software, including the GUI
Successful change implementation should be one of the key objectives of all champions in any organization. It is not easy to reach the “Satisfied State of
Successful Change Deployment” many times
