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.
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.
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.
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.
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.
Mobile Backend as a Service provider AnyPresence continues to hone their chops. Launching the fifth update to their self-titled platform geared for the enterprise. Co-founder Rich Mendis provides some insights for InfoQ readers…
The Behaviour Driven Development, BDD, tool Cucumber is popular in Ruby’s TDD community. It offers a way to write tests that anybody can understand, but is any of the benefits of Cucumber really that beneficial, Kevin Liddle asks in a case against Cucumber. Jon Frisby and Matt Polito has each written a response somewhat arguing against Kevin’s ideas, both seeing benefits in using Cucumber.
Agile has helped us move away from creating upfront requirements but we still have a huge amount of waste with lots of discovery and misunderstandings late in sprints. BDD is meant to decrease this by improving the communication between people working in the problem and solution domains, Matt Wynne states in a recent overview of Behaviour-Driven Development.
Start using Behaviour-Driven Development (BDD) when designing an application and focus on the domain instead of the database, Julie Lerman, a Microsoft MVP since 2003, suggests. BDD lets developers focus on user stories and behaviour in the business domain when building up logic and tests. New to BDD, Julie has implemented a working example using Visual Studio, C# and SpecFlow.
The project for Cucumber, a Behaviour Driven Development, BDD, tool, has recently increased the team and intensive work last months has brought open bugs down substantially, Aslak Hellesøy revealed when talking about the Cucumber ecosystem during a Cucumber conference day last week.
The community research we published on .NET tools and practices had more than 650 votes leading to some interesting results. We attempt to draw insights.
InfoQ's research initiative continues with an 8th question: "What are the most widely used .NET practices and tools?". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.