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.
Behavior Driven Development (BDD) is being increasingly seen as an alternative way to approach Test Driven Development. SpecFlow and NSpec are popular frameworks for BDD in .NET. They help create test specifications that are easy to read even for non-programmers and allow the design of the software to be driven by it’s purpose.
A new form of an old question has been asked in the Behavior Driven Development community: is BDD merely Acceptance Test Driven Development done well? While the community calls out the differences, Dan North makes a request to avoid focusing on them, calling TDD "amazing".
Real Options, a decision-making process based on Financial Option mathematics, was mentioned by Kent Beck in his 1999 "white book," Extreme Progamming Explained. More recently, Agilists have been exploring how Real Options intersects with Agile. Now Chris Matts and Olav Maassen specifically address the Lean Software community, proposing that application of Real Options improves Lean Development.
JetBrains has taken it on themselves to create one of the premier Ruby IDEs on the market. It has been just over 6 months since version 1.0 was released and today, RubyMine 2.0.
It is often the case, a new piece of software is developed by someone who needed to fill a void left by an existing product. Software evolves from tools we use which don't exactly meet our needs, this is the case with a new Behavior Driven Development (BDD) tool called Coulda, developed by Evan Light.