Category tdd

Scratching a JUnit Itch

tl;dr I like JUnit. It is simple and clean, and it is ubiquitous in the Java world. I like Go’s testing package. It is even simpler and cleaner, and distinguishes between failed checks and fatal test failures. It doesn’t use exceptions to do this. I wanted to see what Go’s testing semantics would look like […]

Published: The art of misdirection

I’ve just come back from the excellent NDC 2012 event in Oslo, where they published my article about opportunity cost in The Developer magazine ahead of the conference. The article is now available on my site. Please let me know what you think about it in the comments below.

BDD is like TDD if…

I’ve noticed a number of people recently declaring that BDD really is just TDD, such as Robert Martin on Twitter and Ron Jeffries on the XP list. I can understand where this mindset comes from and I’d like to offer my perspective. Is BDD the same as TDD? Yes. If you’re a programmer, and your entire team is […]

RSpec book in beta

It’s finally happening – I’m writing a book! Well ok, the remarkable David Chelimsky is writing a book. It’s called Behaviour Driven Development with RSpec, Cucumber and Friends and myself and a few other folks are contributing in varying degrees. The book is already in beta, which means you can buy the PDF now from […]

JAOO Australia

A friend of mine has a Far Side desk calendar that he describes it as a barometer for how busy he is. Some days he finds himself tearing off a whole bunch of pages because he’s been too busy or distracted to tear one off each day. I noticed a couple of weeks ago that […]

The End of Endotesting?

…or why Mockito is my new friend. So what’s endotesting? The pioneers of the technique we now know as mocking presented a paper at the XP 2000 conference, where they first introduced the idea to a wider audience. They prefaced it with the quote: bq. “Once,” said the Mock Turtle at last, with a deep […]

JBehave 2.0 is live!

Some ancient history Back in 2003 I started work on a framework called JBehave. It was an experiment to see what JUnit might have looked like if it had been designed from the ground up for TDD rather than as a unit testing framework. I was also starting to use the phrase “behaviour-driven development” to […]

Let your examples flow

Should examples/tests/specs/whatever be DRY(Don’t Repeat Yourself)? I’ve been thinking (and talking and arguing) about the value of test names recently and whether they are just unnecessary duplication, but that’s the subject of a future discussion. This is about the actual content of your examples. So, should your examples be DRY? In a word, no. DRY […]

Awesome Acceptance Testing at SPA 2008

I’ve been pretty slack at letting people know about upcoming talks. I could blame workload or burnout or any number of other plausible-sounding reasons, but a lot of it is just down to not prioritising very well. I should fix that. A couple of years ago Joe Walnes and I gave a talk at an […]

Monkey business value

So I was hanging out with a bunch of geeks in Switzerland, having one of those late night conversations, and an idea sort of emerged, and the more I thought about it, the more I liked the idea. And then I was thinking that a) I’m useless at following through on ideas and b) I […]