Charlie Calvert (surely one of the best-known people in the Delphi community) has written about why Test First Development is such a good thing.

In his opinion, writing the tests first encourages the developer to focus on the architecture - on the external interface and style of use - rather than on the nitty-gritty details. The direct result of this is that the objects are easier to use.

My experience of Test First Development is completely in agreement with this - by starting development with code that runs against the external interface of the class, the focus is on making the class easy to work with, not on making it easy to implement.

If you are interested in knowing more about this subject (and you are using C#/.Net), a good place to start is this recent blog entry.


blog comments powered by Disqus
Next Post
Classic User Interfaces  10 Apr 2004
Prior Post
What makes a Senior Developer?  21 Mar 2004
Related Posts
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
When are you done?  18 Apr 2022
Fixing GitHub Authentication  28 Nov 2021
March 2004