behavior-driven development

Articles

Mushroom cloud explosion How to Ruin Your Behavior-Driven Development Test Scripts

We get it: Writing good, reusable, effective test scripts is hard. It consumes a lot of time and energy, and you have to learn too much about automated testing and test implementation. Just give up and produce some complicated, messy, and ineffective scripts! But why waste time figuring out how to do that on your own? Here are the best practices to ruin your BDD test scripts completely.

László Szegedi's picture László Szegedi
two people with gears moving above heads Behavior-Driven Development and Automation: Establishing Order

Though automation is often mentioned in the same breath as behavior-driven development, they are not equally important. If you want to use behavior-driven development, do just that: Work on getting the approach right, and forget about the automation at first. Here's why you should think of automation as more of a bonus to the BDD process.

Paul Grizzaffi's picture Paul Grizzaffi
The Impact of Quality-Driven Development

When the development and QA teams work independently of each other, there can be some duplication of test efforts—which results in wasted time. The solution: quality-driven development, with QA-implemented automation run in the development environment. This is the story of one team's venture into this new process.

Praveena Ramakrishnan's picture Praveena Ramakrishnan
Divide and Conquer: Find Solutions by Splitting Up

With all of the choices available to software developers, it's easy to become overwhelmed not only by a problem but also by its many possible solutions. One approach that can help you and your team stay on track is to divide and conquer.

Lisa Crispin's picture Lisa Crispin

Conference Presentations

Better Software West 2018, Agile Dev West 2018, DevOps West 2018 Using Behavior Driven Development and Acceptance Test-Driven Development to create GREAT requirements
Slideshow

Defining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, business analysts, developers, and quality assurance experts alike. The origin of many items living in our defect tracking systems can be traced to the difficulties encountered while performing these initial requirements activities. Ken Pugh introduces behavior-driven development (BDD), also known as acceptance test-driven development (ATDD), and explains how it works in creating detailed requirements. He outlines the different roles that team members play in the process. BDD/ATDD has proven to dramatically increase productivity and reduce delays in development by decreasing re-work due to requirement misunderstandings.

Ken Pugh

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.