Pickle adds many convenient Cucumber steps for generating models. Also learn about table diffs in this episode. Cucumber lets software development teams describe how software should behave in plain text. The text is written in a business-readable domain-specific language and serves as documentation, automated tests and development-aid – all rolled into one format. Pickle gives you cucumber steps that create your models easily from factory-girl or machinist factories/blueprints
http://railscasts.com/episodes/186-pickle-with-cucumber

Test-Driven Development (TDD) and Behaviour-Driven Development (BDD) are powerful techniques, helping developers write better designed, more maintainable and more reliable code, and stay focused on the real user requirements. But how does the rest of the team fit in to the picture? In this talk, John Smart, creator of the Java Power Tools Bootcamp, looks at how BDD techniques, and tools such as easyb and FitNesse, can also act as drivers for the overall development process, and also as communication tools, giving testers and end-users clear and unambiguous feedback …

Cucumber is a tool that can execute plain-text functional descriptions as automated tests. The language that Cucumber understands is called Gherkin. While Cucumber can be thought of as a “testing” tool, the intent of the tool is to support BDD. This means that the “tests” (plain text feature descriptions with scenarios) are typically written before anything else and verified by business analysts, domain experts, etc. non technical stakeholders. The production code is then written outside-in, to make the stories pass. Cucumber itself is written in Ruby, but it can be …

In this webcast we’ll introduce Behavior Driven Development (BDD) and Jasmine (a BDD framework for JavaScript); install Jasmine and add related code to the app to support BDD; discuss how to write a failing test first, then add functionality to make a test pass; and finally we’ll develop a simple webOS application test first, with the Mojo SDK.

Dan North gives an overview of Domain Driven Design and Behavior Driven Development then ties them together for a powerful mix.
http://www.infoq.com/presentations/bdd-and-ddd

Acceptance Tests elaborate a user story & are essentially behaviour specifications, expressing examples of how the application will actually be used. These should represent customer-intent in terms the customer understands. This session shows developers and testers how to transcribe their understanding of customer intent in a way that makes sense to customers. Using the popular BDD Given/When/Then approach to acceptance tests, participants will learn how to leverage the popular Fit framework to replicate that approach. Alternatives to using Fit, including using code, will also be explored.
http://skillsmatter.com/podcast/agile-testing/narrative-acceptance-tests-a-behaviour-driven-approach

Behaviour-Driven Development (BDD) started out as a way of teaching Test-Driven Development without getting sidetracked into the complex world of testing. BDD has grown to encompass behaviour at the story level, and is crossing over into the acceptance testing space. This session introduces some of the ideas and vocabulary behind BDD, and demonstrates how you can define acceptance tests from a user perspective as sequences of reusable, executable steps. The intended audience is testers who are looking for effective ways to define and automate their acceptance tests.

UISpec is a Behavior Driven Development framework for the iPhone that provides a full automated testing solution that drives the actual iPhone UI. It is modeled after the very popular RSpec for Ruby. To make finding specific views in the iPhone UI easy, UISpec includes a very powerful view traversal DSL called UIQuery. Not only can you easily traverse the view heirarchy, you can also interact with the views you find.

This screencast shows how to unit test a .NET CLR assembly using Cucumber BDD Framework.

This video provides an experience report on how we build quality software at uSwitch.com. Around 9 months ago the development team shifted from having a separate QA team to adopting a whole-team approach for building and delivering software with quality baked in. This talk explains why we made this shift, provide an insight into how we achieved it from a people and process point of view and delve into tooling. It includes:
- Why testing along the production line is better than testing end-of-cycle.
- How we make sure we get thorough …