Permalink
Browse files

Backported "Why Steak?" section from Steak-2's README

  • Loading branch information...
1 parent 36a26d1 commit 5f7a4bd3a5b8c522cb0d3549ff08cd150ae887dc @cavalle committed Mar 26, 2011
Showing with 10 additions and 0 deletions.
  1. +10 −0 README.rdoc
View
@@ -40,6 +40,16 @@ providing you with the language of acceptance testing (+feature+, +scenario+,
rake task and full Rails integration testing (meaning Webrat support, for
instance)
+== Why Steak?
+
+If, after all, this is just RSpec + Capybara, why does Steak even exist? Do I really need it?
+
+Basically Steak exists for three reasons:
+
+1. *Making a point*. First of all, Steak proposes that using RSpec and Capybara for acceptance testing is a sensible alternative to Cucumber. It also sets a name to refer to that approach.
+2. *Adding convenience*. As a gem, Steak aims to make the experience as convenient as possible. It provides several Rails generators and Rake tasks so that setting up a new project or creating and running specs are quick and seamless tasks. A natural extension of RSpec-Rails.
+3. *Building a community*. No development approach or ruby gem is really valuable without an active community behind it. The mailing list, the IRC channel, the wiki or the twitter account are useful tools to build a community of users that help each other by sharing knowledge, resources and best practices.
+
== Getting started
=== Not in Rails

0 comments on commit 5f7a4bd

Please sign in to comment.