In today’s guest post, Richel Bilderbeek gives us some insight about some the many possible advantages of setting up a continuous integration service, showing some minimal complete examples. Richel works […]
This week’s post is another guest post. Today, Vaughn Cato shares with us some thoughts on writing tests to the code as a variant of TDD. Vaughn works in the […]
For my current project Fix, I use Python and Behave for Behavior Driven Design (BDD). Today I’ll describe my process and the tools I use.
When you accept weakly typed data as input or have them as output, still convert them to strongly typed objects inside your application.
If you have followed my blog, you know that I am a proponent of automated testing. I like TDD and have a very strong opinion about code that has not […]
In the last two weeks I have already written about legacy applications, about how it has to be a team effort and how to plan the refactoring. This week’s post […]
For my current project, some design decisions had to be made to ensure good testability and test coverage.
In last week’s post I wrote about adding a scripting language to our toolset. I focused on the benefits a scripting language like e.g. Python can bring, especially when it […]
One of the more recent posts in my employer’s company blog is titled ‘What’s wrong with: “I don’t write any tests since I am not a tester”?’ – which made me think about the relation of developers to testing, and about the self-image of any developer who would say that sentence in earnest.
Don’t get me wrong. Unit tests are your friends when developing a class. But they should not be that class’ `friend`. Here’s why.