Reputation
3,254
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
1 8 15
Newest
 Custodian
Impact
~112k people reached

Apr
26
revised Side-by-side Functional and Acceptance Testing (SpecFlow)
Turned scenario into a code sample so that it formats correctly
Jan
1
comment How to track technical tasks with BDD?
Just a note: this format isn't really anything to do with BDD. It's the Connextra story template, created by devs at Connextra including Tim McKinnon and Rachel Davies, and predates BDD.
Jan
1
awarded  Custodian
Jan
1
reviewed Close If TDD is about design why do I need it?
Jan
1
reviewed Leave Open How should a service communicate with an activity in real-time?
Dec
8
awarded  Nice Answer
Sep
9
awarded  Yearling
Aug
13
comment Design patterns - do you use them?
@AaronHall Thank you! Much appreciated; I like me some shinies.
Aug
13
awarded  Great Answer
Jul
29
answered Which style to use for features that are not directly driven by humans when using BDD Gherkin language?
Jul
20
comment BDD, Cucumber best practices
@Soru Agreed, but you can still do BDD at a unit level, exploring the behaviour of classes and methods instead of systems. We took the capability out of JBehave 2 because it was possible and easier with JUnit. Here's an NUnit example, showing the Given / When / Then in comments: github.com/lunivore/WiPFlash/blob/master/WiPFlash.Behavior/…
Jul
18
comment BDD, Cucumber best practices
@Soru I wrote a bit more about the move from class-level examples to system-level scenarios, and Chris Matts' involvement, here: lizkeogh.com/2011/06/27/… - please pass this on to whoever gave you your version of history.
Jul
18
comment BDD, Cucumber best practices
@Soru Dan North created JBehave back in 2004. He ported it to Ruby, which became RBehave, which became RSpec's story runner, which became Cucumber. And originally it was a replacement for JUnit. I know this because I helped him write JBehave 1.0 and the core of JBehave 2.0. Dan's introductory post also talks explicitly about how he started BDD as a replacement for TDD, and the use of the word "should" instead of "test": dannorth.net/introducing-bdd
Jul
16
comment BDD, Cucumber best practices
BDD actually started as a way of looking at the behaviour of classes, rather than systems; JBehave (the first BDD tool) was originally a replacement for JUnit.
Jul
16
answered BDD, Cucumber best practices
May
14
comment BDD: Is it wrong to call it “Behaviour Driven *Design*”?
@RobertHarvey We care a lot more about the results than we do about what people call it. So I wouldn't worry too much. My hat is hanging over here: infoq.com/presentations/Learning-and-Perverse-Incentives
May
13
comment BDD: Is it wrong to call it “Behaviour Driven *Design*”?
Most inexperienced developers might, but it's their role that's poorly titled, since they're usually coders or programmers. I can promise that testers and analysts don't make that assumption, nor does the Head of Development in your org, and it's that person we're really trying to sell it to.
May
13
comment BDD: Is it wrong to call it “Behaviour Driven *Design*”?
@RobertHarvey "Development" in this sense refers to the entire software development lifecycle. Otherwise we'd have called it Behaviour-Driven Programming.
May
13
answered BDD: Is it wrong to call it “Behaviour Driven *Design*”?
Apr
17
comment How to use unit tests when using BDD?
The author of the article is Dan North, who came up with the concept in the first place. One of the things he noticed is that the word "test" causes us to move to testing our implementation (solution domain) whereas actually, exploring and defining tests should really keep us in the problem domain. Dan has described BDD as "what TDD was meant to be". Read this for more info: dannorth.net/2012/05/31/bdd-is-like-tdd-if