Working Effectively with Legacy Code

This book covers the adoption of Unit Testing and TDD into existing (Legacy) applications.
The author defines Legacy code to be any code not covered by unit tests (which is rather strict).
He also insists that individual unit tests that take 0.1 seconds are slow.
This prevents unit tests from relying upon databases.

I have a slight problem with implementing that – the main projects that I work on have a fair amount
of stored procedure code. These need unit test coverage (plus the interfaces with the rest of the code also needs to be tested).

The book also provides strategies to get Legacy code under test.

Referenced Book:

Rober C Martin’s Agile Software Development : Principles, Patterns and Practices (Pearson Education, 2002).

Leave a Reply

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

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

Facebook photo

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

Connecting to %s