odiop.blogg.se - Coaches eye for windows and mac

Studying about mock objects led me to jMock. Here’s a peek at my bookshelf, with the programming books that have influenced me the most. Once I learned how to add unit tests to legacy code, everything opened up. This book gave me techniques for making existing code testable.

This helped me with the greenfield project, but what could I do about legacy code? Along came another book: Working Effectively with Legacy Code by Michael Feathers.

There was a problem with Refactoring: it presumed the existence of unit tests.

The talk was riveting: how to safely change software by following predetermined recipes. There, I listened to Martin Fowler introduce his new book Refactoring.

I attended SD, the software development conference hosted by Dr.

This was nowhere near the disciplines of Test-Driven Development I’ve since learned.

When I had a chance to work on a greenfield project, I took my first stab at doing it test-first.

This was my first foray into discovering how tooling could make test code easier to write and manage. Making my own unit testing framework taught me a lot about how they work.

Back then, there was no platform support for unit testing frameworks, so you just used whatever you could find or make.