https://github.com/doabit/capybara-padrino

Capybara and rspec config for padrino
https://github.com/doabit/capybara-padrino

Last synced: about 1 month ago
JSON representation

Capybara and rspec config for padrino

• Host: GitHub
• URL: https://github.com/doabit/capybara-padrino
• Owner: doabit
• License: mit
• Created: 2013-04-09T01:41:17.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2013-04-09T02:15:11.000Z (over 11 years ago)
• Last Synced: 2024-09-14T02:50:00.664Z (2 months ago)
• Language: Ruby
• Size: 166 KB
• Stars: 3
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# Capybara::Padrino

Capybara and rspec config for padrino.

## Installation

Add this line to your application's Gemfile:

    group :test do

      gem "capybara-padrino"

    end

Or

    group :test do

      gem "capybara-padrino", github: "doabit/capybara-padrino"

    end

And then execute:

    $ bundle

## Usage

If you are using rspec, and don't want to write ":type => :feature" for every feature spec, then add

     require "capybara/padrino/rspec"

in spec_helper.rb. Now put your Capybara specs in spec/features and write your specs like so:

    describe "the signup process" do

      before :each do

        User.make(:email => '[email protected]', :password => 'caplin')

      end

      it "signs me in" do

        visit '/sessions/new'

        within("#session") do

          fill_in 'Login', :with => '[email protected]'

          fill_in 'Password', :with => 'password'

        end

        click_link 'Sign in'

        page.should have_content 'Success'

      end

    end

## Contributing

1. Fork it

2. Create your feature branch (`git checkout -b my-new-feature`)

3. Commit your changes (`git commit -am 'Add some feature'`)

4. Push to the branch (`git push origin my-new-feature`)

5. Create new Pull Request

π