From c7794ad1652141fba1307b0602a842c510ea1974 Mon Sep 17 00:00:00 2001
From: Josh Rendek <josh@bluescripts.net>
Date: Mon, 21 Nov 2011 18:46:56 -0700
Subject: [PATCH] improves Cucumber documentation in README

---
 README.textile | 35 +++++++++++++++++++++++++++++++++--
 1 file changed, 33 insertions(+), 2 deletions(-)

diff --git a/README.textile b/README.textile
index 2f10bc4..a007c90 100644
--- a/README.textile
+++ b/README.textile
@@ -70,7 +70,7 @@ strategy the remaining time.  To accomplish this you can say:
   # then make the DatabaseCleaner.start and DatabaseCleaner.clean calls appropriately
 </pre>
 
-Example usage with RSpec:
+h3. RSpec Example
 
 <pre>
 RSpec.configure do |config|
@@ -91,7 +91,38 @@ RSpec.configure do |config|
 end
 </pre>
 
-For use in Cucumber please see the section below.
+h3. Cucumber Example
+
+Add this to your features/support/env.rb file:
+
+<pre>
+begin
+  require 'database_cleaner'
+  require 'database_cleaner/cucumber'
+  DatabaseCleaner.strategy = :truncation
+rescue NameError
+  raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it."
+end
+</pre>
+
+A good idea is to create the before and after hooks to use the DatabaseCleaner.start and DatabaseCleaner.clean methods.
+
+Inside features/support/hooks.rb:
+
+<pre>
+Before do
+  DatabaseCleaner.start
+end
+
+After do |scenario|
+  DatabaseCleaner.clean
+end
+</pre>
+
+This should cover the basics of tear down between scenarios and keeping your database clean. 
+For more examples see the section "Why?"
+
+h2. Common Errors
 
 In rare cases DatabaseCleaner will encounter errors that it will log.  By default it uses STDOUT set to the ERROR level but you can configure this to use whatever Logger you desire.  Here's an example of using the Rails.logger in env.rb: