In the beginning of my career, I discovered that having automated tests is invaluable when making changes to any non-trivial software system. Or, put differently, I realized that changing a non-trivial software system without having the support of a suite of automated tests is both risky and time consuming.

A while back, I got fed up with writing code. Not writing code in general, mind you, but I did face a situation where I needed to write a lot of boilerplate code, and having to write such code is a certain way of losing interest in software development. Not …

I recently came across a thread discussing Test-Driven Development (TDD) on one of the major social networks. The discussion revolved around when to use TDD and when it can be skipped. As a consistent TDD practitioner, I find these discussions interesting, especially when it comes to understanding the perspectives of …

Can you combine Test-Driven Development (TDD) with prototyping? How can you write tests for functionality that is largely unknown? Where do you even start if you’re on unfamiliar ground and you need to explore to learn about possibilities and constraints? How can you write tests when you don’t …

Test-Driven Development (TDD) is a programming practice that to me is an immensely useful quality assurance tool. In brief, TDD is about writing unit tests first and letting the unit tests drive the design of your code. Some of the most important benefits are:

• The public API your create becomes …