BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Behavior Driven Development Content on InfoQ

  • DDD and Living Documentation

    Creating documentation is boring, it's often obsolete and misleading but with a new mindset both your documentation and code can improve, Cyrille Martraire explained in a presentation showing how to create living documentation when working with Domain-Driven Design (DDD) at this year’s DDD Exchange conference in London.

  • Dan North Asks for Real World BDD Examples

    During a panel discussion about Behaviour-Driven Development (BDD) at this year’s CukeUp 2015 conference Dan North came up with an idea of a community-curated resource for everyone interested in BDD with examples, adaptions, scenarios as well as experience reports and common practises and links to other external resources.

  • How BDD Has Helped to Address Communication Problems and Improve Collaboration

    Behavior driven development (BDD) can be used to improve communication between testers, developers and the business. For example you can use given-when-then scenarios to develop test scripts and at the same time define the requirements of the system. BDD involves all team members and helps them to think about the product.

  • BDD is a Centred Rather than a Bounded Community

    At the recent CukeUp 2015 conference an attempt was made to describe what Behaviour-Driven Development (BDD) actually is, and for Paul Rayner it was clear that BDD is a community centred on key values and principles still open to adding new practices, not a community focused on boundaries and exclusion.

  • Experiment using Behavior Driven Development

    Behavior Driven Development (BDD) uses examples, preferably in conversations, to illustrate behavior. A lot of people focus on the tools if they are doing BDD but having the conversations is more important than writing down conversations and automating them said to Liz Keogh. An exploration of using BDD to do experiments to deal with complex problems and do discoveries.

  • BDD Tool Cucumber is Not a Testing Tool

    Cucumber was created as a way to overcome ambiguous requirements and misunderstandings, targeting both non-technical and technical members of a project team, but if you think Cucumber is a testing tool you are wrong, Aslak Hellesøy, who created Cucumber in 2008, recently stated. Julien Biezemans and Liz Keogh recently expressed similar opinions.

  • Why BDD Can Save Agile

    Matt Wynne, founder at Cucumber Ltd spoke at QCon London 2015 on how BDD can leverage the benefits of Agile on teams struggling with common patterns like lack of predictability, communication and quality.

  • Behaviour-Driven Development Combined with Domain-Driven Design

    Behaviour-Driven Development (BDD) is very much about conversations and examples but there is a software design part that can be used to bring BDD and Domain-Driven Design (DDD) practices together, combining the conversional bits with a domain-focused design activity, Konstantin Kudryashov explains in a presentation.

  • Introducing Behaviour-Driven Development

    Behaviour-Driven Development (BDD) can help in overcoming the gap between the developer’s understanding of what needs to be built and the business’ understanding of the technical challenges caused by the requirements. The reason is improvement in communication between the two groups, Alistair Stead and Konstantin Kudryashov explains in their Beginner’s guide to BDD.

  • Embedding Security Testing in Development Workflow

    Stephen de Vries, ContinuumSecurity founder, promoted the idea of continuous and visible security at Velocity Europe 2014. Stephen argued that the same kind of processes and tools that embedded QA in the whole workflow of an agile development process can be applied to security. BDD-Security is a security testing framework that follows the Given-When-Then approach and is built on top of JBehave.

  • Behaviour Driven Development Is About Conversation Not Tooling

    The single most important of Behaviour-Driven Development (BDD) is the conversation, not the tooling, Liz Koegh states in a presentation about 10 years of doing BDD at the recent Cucumber conference. Liz believes we have made some big mistakes during these years of practicing BDD, but she is quite excited about some of the developments over the last few years.

  • Cucumber.js for BDD in JavaScript: An Interview with Julien Biezemans

    Julien Biezemans is a Cucumber core team member and the author of Cucumber.js. Cucumber.js is a native JavaScript implementation of Cucumber, and is a strict port that can run on any JavaScript environment. Running on Node.js as well as within any browsers, Cucumber.js is virtually serviceable against everything producing JavaScript and HTML (Node.js, Ruby on Rails, PHP, .NET, etc)

  • BDD and JavaScript Using CucumberJS

    Adding CucumberJS to the TDD workflow for JavaScript-based projects embraces the ideas of Behaviour Driven Development, BDD, and allows a developer to follow the TDD principles while developing from the outside in; running automated tests that fail until code that supports a feature is implemented, Todd Anderson reveals in a recent blog post.

  • Behaviour-Driven Development: Value through Collaboration

    The goal of a software project is to deliver value to stakeholders and Behaviour-Driven Development, (BDD), is designed for that, Viktor Farcic, a software developer working on transitions from waterfall to agile processes, states in the first of four blog posts describing his view on BDD.

  • Behaviour-Driven Development Tool Jasmine 2.0 Released

    The recently released version 2.0 of Jasmine, a Behaviour-Driven Development, BDD, testing framework for JavaScript, comes with improved support for Node.js, major work on increasing the internal quality and some backwards compatibility breaking changes.

BT