designing for testability

Achieving And Recognizing Testable Software Designs is part 1 of a series of articles in which Roy Osherove looks at design for testability. This first part defines “testability”, and then gives a few examples in which Roy refactors C# code to improve its testability. Clear and concise and well worth a read. I’ll be looking out for the next installment.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s