Tag: bdd

  • Continuous delivery – the novel

    Continuous delivery – the novel

    I find myself recommending the same books over and over again. When speaking to techies I invariably recommend GOOS; when speaking to managers The Mythical Man Month or Waltzing With Bears. Over the past year or two, I’ve also pointed a lot of organisations at Continuous Delivery by Jez Humble and Dave Farley. It’s an…

  • Teaching TDD (TTDD)

    Teaching TDD (TTDD)

    There has been a flurry of discussion about how to teach TDD, sparked off by a recent post from Justin Searls. In it he lists a number of failures that range from “Encouraging costly Extract refactors” to “Making a mess with mocks” all of which distract attention from the concept that “TDD’s primary benefit is…

  • Eat your own dogma food

    Eat your own dogma food

    The software development community experiences fad after fad. Consultants and thought leaders dream up new methodologies; old practices are relabelled and promoted as the next big thing; flame wars are fought over names, tabs and brace position. One of the few practices that has stood the test of time is that of “eating your own…

  • TDD at interviews

    TDD at interviews

    Allan Kelly posted an article on DZone this week predicting that TDD would be a required skill for developers by 2022. Vishal Biyani asked on Twitter about how one might test TDD skills, and I promised to blog about my experience of using Cyber-Dojo in interview situations. Cyber-Dojo is a browser-based dojo environment developed by…

  • When is a tester not a tester?

    When is a tester not a tester?

    No, I’m not trawling through my xmas cracker jokes. I was looking through the programme for DevWeek 2014 and both my sessions are tagged as “Test”. This is following a pattern started at ScanDev last year and followed by several other conferences at home and abroad. Why am I bothered? It’s not that I mind…

  • Aslak’s view of BDD, Cucumber and automated testing

    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…

  • The context and definition challenge

    The context and definition challenge

    We’re very good at rationalising. Almost any statement can be justified by the retroactive application of the twin constraints of “context” and “definition.” As an example, Chris Matts (@papachrismatts) talked about the “death of Agile” in a recent blog post of his, and I took issue with that. We talked about it briefly at a…

  • Tax or investment – which do you prefer?

    Tax or investment – which do you prefer?

    I was working with a client last week who were trying to fit some new technical practices into their daily routine. The way they were trying to ‘account’ for this in their iteration planning was by introducing a 10% ‘tax’ on their velocity. In other words, they were reducing the number of story points that…

  • Dan North – an open letter

    Dan North – an open letter

    Welcome to another post in my “Death of agile” series. This post is an open letter to Dan North, the ‘father’ of BDD. See also: Death of agile Open letter to Chris Matts Open letter to Gabriel Steinhardt Dear Dan, I’ve been meaning to talk to you about some of your recent conference keynotes, specifically…

  • Be pure. Be vigilant. Behave.

    There has been a bit of traffic on the Growing Object Oriented Software (GOOS) mailing list recently about how many tests you should write, and what sort they should be. Understandably it got back to the perennial discussion about what constitutes a unit test, what an integration test, what an acceptance test. And where does…