Skip to content

Commit

Permalink
Explain why Capybara is useful. closes #818
Browse files Browse the repository at this point in the history
  • Loading branch information
jnicklas committed Sep 28, 2012
1 parent ba0f3d9 commit 732e6f1
Showing 1 changed file with 13 additions and 4 deletions.
17 changes: 13 additions & 4 deletions README.md
Expand Up @@ -4,14 +4,23 @@
[![Dependency Status](https://gemnasium.com/jnicklas/capybara.png)](https://gemnasium.com/jnicklas/capybara)
[![Code Quality](https://codeclimate.com/badge.png)](https://codeclimate.com/github/jnicklas/capybara)

Capybara helps you test Rails and Rack applications by simulating how a real
user would interact with your app. It is agnostic about the driver running your
tests and comes with Rack::Test and Selenium support built in. WebKit is
supported through an external gem.
Capybara helps you test web applications by simulating how a real user would
interact with your app. It is agnostic about the driver running your tests and
comes with Rack::Test and Selenium support built in. WebKit is supported
through an external gem.

**Need help?** Ask on the mailing list (please do not open an issue on
GitHub): http://groups.google.com/group/ruby-capybara

## Key benefits

- **No setup** necessary for Rails and Rack application. Works out of the box.
- **Intuitive API** which mimics the language an actual user would use.
- **Switch the backend** your tests run against from fast headless mode
to an actual browser with no changes to your tests.
- **Powerful synchronization** features mean you never have to manually wait
for aynchronous processes to complete.

## Setup

To install, type
Expand Down

0 comments on commit 732e6f1

Please sign in to comment.