Found another good article on the practicalities for Test Driven Development. This one is about Mock Objects.
The minute after you start to think about doing TDD through all your code you find yourself pondering about how to test only the current layer. For example the business layer has references to the Data Access layer (as it often do) but i only want to test the business layer. This is solve by Mock objects, which the article is about.
Also some issues about configuration arises. Like; how can i assure that the mocked objects are used in a test run but now in a debug run... There are some references about that also in the article.
If you liked this post ... here's more for you:
Published byon Last updated