By MortazaviBlog on Jan 17, 2007
The cost savings and efficiencies of Test-Driven Development (TDD) should be clear not just to any hardware engineer but also to software and other engineers, system designers and developers. In fact, even when we imagine we are developing without a test, we implicitly have some kind of test in mind: We build systems in order to elicit specific responses to specific stimuli (tests?) upon those systems. Most software developers know how a good test can drive their work, particularly when the system is complex with multitude of constraints and also when there are volumes of existing tests to detect regressions.