Behavior-Driven Development (BDD) agile testing articles, tools, tutorials and videos.

Acceptance Testing with Thucydide and Spring

September 30, 2011 0

Thucydides is an open source tool that lets you use WebDriver-based unit or Behavior Driven Development (BDD) tests to write more flexible and more reusable WebDriver-based tests, and also to generate documentation about your acceptance tests. In this blog post, John Ferguson Smart explains how you can use Spring dependencies in your acceptance tests with Thucydides if you need to run your acceptance tests against an embedded web server.

BDD with Specflow, Moq and Microsoft Unit Testing framework

August 18, 2011 0

This blog post explains how to use Specflow, Moq and Microsoft Unit Testing framework to implement Behavior Driven Development in a .NET context. The author used AAA (Arrange-Act-Assert) and GWT (Given-When-Then) patterns in his code. They are clearly and easily to understand and become standard when you write unit testing and mocking.

Behavior Driven Development Using SpecFlow and WebAii

March 29, 2011 0

SpecFlow provides a pragmatic and frictionless approach to Acceptance Test Driven Development and Behavior Driven Development for .NET projects . This video shows how to use SpecFlow to create specifications and leverage Telerik’s WebAii Test Automation Framework for driving the browser through code. Download the video on Develop Using .NET

Cucumber versus Steak

January 31, 2011 0

Iain Hecker discuses the way to describe behavior in Cucumber compared to the simpler option provided by Steak. Cucumber and Steak are two open source ruby behavior driven development (BDD) tools.

The Principle of Symmetric Change

December 6, 2010 0

Many of the most common problems people have with implementing BDD or agile acceptance testing come from a misalignment of conceptual models. By changing our view at the specifications/tests we can make most of those issues go away instantly. This post explains the principle of symmetric change: one small change in a business model should require one small change to executable specifications.

1 4 5 6 7