Black box testing in feature files.

"CLI Steps for Cucumber".

I'm unconvinced this is a good solution - in fact I think it breaks the whole idea of continuous integration. I think it would be better to look at other ways to have a test suite that ran fast enough that each developer is happy to run it locally.

I like the more OO approach, but something still doesn't feel quite right to me.

I note that it uses screen objects as an abstraction technique. I approve of this bit at least.

"Simply Agile by Andrew Bruce is an open source agile software project management application. Think of a simple version of Pivotal Tracker. You can add story cards to a backlog, and then assign each card to a sprint. Each time a card is completed you can drag and drop it to the appropriate column in the Simply Agile task board. Andrew has a very dedicated approach to test-driven development and as a result the application is well covered by cucumber and rspec tests. The javascript in this application is written in an unobtrusive style and is a good example of using jQuery for "progressive enhancement". The app is fully functional in browsers without javascript, but where javascript is available so is the drag-and-drop interface."

"Features: Cucumber integration tests, Rspec coverage, Drag and drop interface powered by jQuery."

"Written in a very modern way featuring examples of using Cucumber for integration testing, a simple Rack middleware example and an interesting routes.rb file showing how to cleanly version an API".

Using Cucumber and Selenium to do browser testing in the cloud.

"A new awesome BDD framework that features encapsulation and modularity of your step definitions".

I agree with much, but not all, of this.

I'm not convinced...

"Pickle gives you cucumber steps that create your models easily from factory-girl or machinist factories/blueprints. You can also just use ActiveRecord as a factory but it’s not as cool".

So if Cucumber sucks, but a higher level of abstraction in your acceptance tests is desirable, why not do the abstraction in Ruby and not in regular expressions?

"A test suite based on Cucumber and Cucumber-Nagios for testing and monitoring telephony systems".

"Easily handle JSON in RSpec and Cucumber".

"Distributed Cucumbers".

"A comprehensive guide to testing Rails applications, covering Test-Driven Development from both a theoretical perspective (why to test) and from a practical perspective (how to test effectively). It covers the core Rails testing tools and procedures for Rails 2 and Rails 3, and introduces popular add-ons, including Cucumber, Shoulda, Machinist, Mocha, and Rcov."

Because it's mental.

A DRb server for testing frameworks (RSpec / Cucumber currently) that forks before each run to ensure a clean testing state.

Cucumber scenarios as documentation.

"Relish allows you to browse, search, and organize your Cucumber features on the web."

"A koan for creating your own simple mocking framework in Ruby".

"Courgette is a Rails engine (plugin) for Rails 2.x applications which makes your cucumber features files viewable through your browser". Reminds me of "whereuat".

Question from Chris about why the envjs codebase used by capybara-envjs has diverged from the Rhino related version of envjs.

Similar concerns to those I aired in my own blog post about Cucumber.

"An internal DSL that is similar to RSpec StoryRunner, the predecessor of Cucumber's Gherkin external DSL". I'm not convinced about labelling each Given, When & Then with text - but perhaps you can leave these out and just use code blocks?

"Distributed Rspec & Cucumber via Bonjour".

"My experience with Fit and other agile acceptance testing tools is that they cost more than they're worth. There's a lot of value in getting concrete examples from real customers and business experts; not so much value in using "natural language" tools like Fit and similar."

Example using Rspec & Cucumber.

"Story card app for railsconf 2010 demo".

"Allows you to write integration tests for your iPhone applications without changing your existing code (as long as your application makes proper use of the accessibility APIs)". Uses AppleScript like in my RubyManor talk.

"Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests". Nice use of metaphor.

"Minimalist acceptance testing on top of RSpec". An alternative to Cucumber.

"Synchronize user stories in Pivotal Tracker with Cucumber features".

Pickle makes life in the Cucumber world so much easier by providing you with convenient step definitions that take care of common object operations leaving you free to focus on the fun stuff. Combined with the pre-packaged Webrat steps you can dramatically reduce the number of step definitions you need to write.

Pickle allows you to easily create objects from your factories (Factory Girl), blueprints (Machinist) or ActiveRecord.

"Lets you describe how a website should work in plain text, and outputs whether it does in the Nagios plugin format".

"Easy model creation/reference in cucumber - optionally leveraging your factories/blueprints".

"Coulda gives you Cucumber-like BDD power but with an internal DSL. This means no "call-by-regexp" and no Gherkin/plain-text/external DSL. Coulda is just code — but with a Cucumber-like take on BDD".

"Integration tests are a scam - a self-replicating virus that threatens to infect your code base, your project, and your team with endless pain and suffering". Expresses some of my previous (pre-Ruby/Rails) experience with integration tests. Offers an interesting counterpoint to the latest Ruby/Rails love affair with integration tests. I keep meaning to write something up about this.

Acceptance testing for the iPhone.

"Lazy coverage-aware running of Cucumber acceptance tests".

Tutorial.

Culerity integrates Cucumber and Celerity in order to test your application's full stack including Javascript. Your Rails app doesn't have to run in JRuby.

Examples using celerity, cucumber, and rspec to verify web application behaviour, including javascript and AJAX.

I've been thinking along similar lines recently. I think the thing I like about Cucumber is Webrat and I think I could do without the English language abstraction.

TextMate bundle for Cucumber.

"Collection of rspec matchers and cucumber steps for testing email in a rails app".

Cucumber steps and RSpec matchers, etc for testing email.

Getting started with Cucumber and Rails.

Distributed test running with auto-discovery via Bonjour (for Cucumber first).

A tool that can execute feature documentation written in plain text. Targets non technical business analysts, interaction designers, domain experts, testers (for the plain text part) and programmers (for the steps, which are written in Ruby).