- All posts are released under CC 3.0 by-sa unless otherwise stated.
Pages
Follow me on Twitter!
My Tweets-
Recent Posts
Recent Comments
Categories
- bdd
- breaking models
- business value
- capability red
- coaching
- complexity
- conference
- csharp
- cynefin
- deliberate discovery
- evil hat
- feedback
- humour
- jbehave
- kanban
- lean
- learning
- learning models
- life
- nlp
- open source
- real options
- scale
- scrum
- spike and stabilize
- stakeholders
- stories
- testing
- Uncategorized
- uncertainty
- values
- writing
Archives
Meta
Tag Archives: bdd
Tyburn 1.0 released
It seems to be the season for releasing code! Tyburn is a fast, minimal, extensible Java Swing harness that was originally part of JBehave 1.0. You can download it here and use it like this: WindowControl control = new WindowControl(“my.named.frame”); … Continue reading
JBehave 2.0 is released!
We discovered some time ago that JBehave 1.0 wasn’t being used. When we found out that it took over an hour to write the scenarios for the Game of Life, we realised why. Our goal with JBehave 2 was to … Continue reading
JBehave 2 is up on its usual svn
svn co http://svn.codehaus.org/jbehave/trunk No ‘official releases’ yet, but if you want to play, go ahead. Examples of examples are checked into trunk. Features include: plain text scenarios steps defined using annotations that match the scenarios built on JUnit Ensure (which … Continue reading
Bug Driven Development: a danger of delivering the pretty GUIs first
After my last post, Negin and I were quite pleased that we’d got as far as we had. So was our Business Analyst. “So, this story that was estimated at 3 days,” she said. “Can I say it’s only taken … Continue reading
BDD: Bug Driven Development
Today, Negin and I paired on a brand new piece of work. “We’ll need to create this domain object,” she said, “and a database table.” “I don’t want to do that,” I said. “I’d rather fix the stuff that’s broken.” … Continue reading
Crazy like a fox.
At my current client, everyone loves BDD, and everyone starts their tests with the word ‘should’, describing the behaviour of the associated class. I’m currently looking at this code: public class PrimaryMixingIteratorTest extends EasyMockObjectTestBase{ public void testShouldIterateLikeAFox() throws Exception { … Continue reading
Liz Keogh, lunivore 