Category: BDD
-
Unit tests are your specification
Recently a Schalk Cronjé forwarded me a tweet from Joshua Lewis about some unit tests he’d written. . @ysb33r I’m interested in your opinion on how expressive these tests are as documentation https://t.co/YpB1A3snUV /@DeveloperUG — Joshua Lewis (@joshilewis) December 3, 2015 I took a quick look and thought I may as well turn my comments…
-
Diamond recycling (and painting yourself into a corner)
The post I wrote recently on recycling tests in TDD got quite a few responses. I’m going to take this opportunity to respond to some of the points that got raised. Do we really need to use the term “recycling”? The TDD cycle as popularly taught includes the instruction to “write a failing test”. The point…
-
Recycling tests in TDD
The standard way that TDD is described is as Red-Green-Refactor: Red: write a failing test Green: get it to pass as quickly as possible Refactor: improve the design, using the tests as a safety net Repeat TL;DR; I’ve found that step 1) might be better expressed as: Red: write a failing test, or make an…
-
Using SpecFlow on Mono from the command line
SpecFlow is the open source port of Cucumber for folk developing under .NET. It has been compatible with Mono (the open source, cross platform implementation of the .NET framework) for several years, but most of the documentation talks about using it from within the MonoDevelop IDE. I wanted to offer SpecFlow as one of the…
-
Aslak’s view of BDD, Cucumber and automated testing
This is a quote from Aslak Hellesoy on the Cukes Google group. “Even on this list, the majority of people seem to think that Cucumber == Automated Tests == BDD, which is WRONG. What people need to understand is: Cucumber is a tool for BDD Cucumber is a tool for Specification By Example Specification By…