Test first

Over the last 30 years, there have been a number of approaches to software development that have attempted to help engineers ‘build quality in’ to a system, rather than leaving testing to the end of a cycle. From Design by Contract to Test Driven Development, Behaviour Driven Development and Acceptance Test Driven Development, they are all approaches that encourage engineers and developers to think about the testing of a piece of functionality before any code has been written. User stories have evolved to do something similar. It’s been proven to improve the quality and output of a development process.


How do you know the thing you’re working on today or this week is successful? What test might you run to validate if it worked or not?

Related content