capybara5--实现你第一个自动化场景

describe "i want search capybara",  :type => :feature do


    context 'i need to open browser' do
      it 'should be  has an browser'

  end
    context 'when i input baidu url into the browser textarea' do
      it 'should be redirect  to the baidu homepage'
  end
    context 'when i input the capybara into search text ' do
      it 'responds with 200 and show the result'

  end
end

rails generate rspec:install

.rspec
spec/spec_helper.rb
spec/rails_helper.rb

require "capybara/rspec"
require "capybara"
require "rspec"
require 'pry'

Capybara.default_driver = :selenium
Capybara.app_host = 'http://www.baidu.com'

Capybara.register_driver :selenium do |app| Capybara::Selenium::Driver.new(
app, :browser => :chrome )
end

# This file was generated by the `rspec --init` command. Conventionally, all
# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
# The generated `.rspec` file contains `--require spec_helper` which will cause
# this file to always be loaded, without a need to explicitly require it in any
# files.
#
# Given that it is always loaded, you are encouraged to keep this file as
# light-weight as possible. Requiring heavyweight dependencies from this file
# will add to the boot time of your test suite on EVERY test run, even for an
# individual file that may not need all of that loaded. Instead, consider making
# a separate helper file that requires the additional dependencies and performs
# the additional setup, and require it from the spec files that actually need
# it.
#
# The `.rspec` file also contains a few flags that are not defaults but that
# users commonly want.
#
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
RSpec.configure do |config|

  # rspec-expectations config goes here. You can use an alternate
  # assertion/expectation library such as wrong or the stdlib/minitest
  # assertions if you prefer.

  config.expect_with :rspec do |expectations|
    # This option will default to `true` in RSpec 4. It makes the `description`
    # and `failure_message` of custom matchers include text for helper methods
    # defined using `chain`, e.g.:
    #     be_bigger_than(2).and_smaller_than(4).description
    #     # => "be bigger than 2 and smaller than 4"
    # ...rather than:
    #     # => "be bigger than 2"
    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
  end

  # rspec-mocks config goes here. You can use an alternate test double
  # library (such as bogus or mocha) by changing the `mock_with` option here.
  config.mock_with :rspec do |mocks|
    # Prevents you from mocking or stubbing a method that does not exist on
    # a real object. This is generally recommended, and will default to
    # `true` in RSpec 4.
    mocks.verify_partial_doubles = true
  end

  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
  # have no way to turn it off -- the option exists only for backwards
  # compatibility in RSpec 3). It causes shared context metadata to be
  # inherited by the metadata hash of host groups and examples, rather than
  # triggering implicit auto-inclusion in groups with matching metadata.
  config.shared_context_metadata_behavior = :apply_to_host_groups

# The settings below are suggested to provide a good initial experience
# with RSpec, but feel free to customize to your heart's content.
=begin
  # This allows you to limit a spec run to individual examples or groups
  # you care about by tagging them with `:focus` metadata. When nothing
  # is tagged with `:focus`, all examples get run. RSpec also provides
  # aliases for `it`, `describe`, and `context` that include `:focus`
  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
  config.filter_run_when_matching :focus

  # Allows RSpec to persist some state between runs in order to support
  # the `--only-failures` and `--next-failure` CLI options. We recommend
  # you configure your source control system to ignore this file.
  config.example_status_persistence_file_path = "spec/examples.txt"

  # Limits the available syntax to the non-monkey patched syntax that is
  # recommended. For more details, see:
  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
  config.disable_monkey_patching!

  # This setting enables warnings. It's recommended, but in some cases may
  # be too noisy due to issues in dependencies.
  config.warnings = true

  # Many RSpec users commonly either run the entire suite or an individual
  # file, and it's useful to allow more verbose output when running an
  # individual spec file.
  if config.files_to_run.one?
    # Use the documentation formatter for detailed output,
    # unless a formatter has already been configured
    # (e.g. via a command-line flag).
    config.default_formatter = 'doc'
  end

  # Print the 10 slowest examples and example groups at the
  # end of the spec run, to help surface which specs are running
  # particularly slow.
  config.profile_examples = 10

  # Run specs in random order to surface order dependencies. If you find an
  # order dependency and want to debug it, you can fix the order by providing
  # the seed, which is printed after each run.
  #     --seed 1234
  config.order = :random

  # Seed global randomization in this process using the `--seed` CLI option.
  # Setting this allows you to use `--seed` to deterministically reproduce
  # test failures related to randomization by passing the same `--seed` value
  # as the one that triggered the failure.
  Kernel.srand config.seed
=end
end

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [22:00:31]
$ rspec ./spec/features/baidusearch_spec.rb
***

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) i want search capybara i need to open browser should be  has an browser
     # Not yet implemented
     # ./spec/features/bb_spec.rb:9

  2) i want search capybara when i input baidu url into the browser textarea should be redirect  to the baidu homepage
     # Not yet implemented
     # ./spec/features/bb_spec.rb:16

  3) i want search capybara when i input the capybara into search text  responds with 200 and show the result
     # Not yet implemented
     # ./spec/features/bb_spec.rb:20


Finished in 0.00059 seconds (files took 1.37 seconds to load)
3 examples, 0 failures, 3 pending

describe "i want search capybara",  :type => :feature do
  context "the page" do

    before do
      page.driver.browser.manage.window.resize_to(1440,900) #Mention it here
      visit "/"

    end

    context 'i need to open browser' do
      it 'should be  has an browser' do
      expect(page.driver.browser.browser).to eq :chrome
    end
  end
    context 'when i input baidu url into the browser textarea' do
      it 'should be redirect  to the baidu homepage' do
       expect(page.driver.current_url).to eq('https://www.baidu.com/')
    end
end
    context 'when i input the capybara into search text ' do
      it ' show search the result' do
        fill_in 'kw', :with => 'capybara'
        click_button '百度一下'
        expect(page).to have_content 'Capybara - Wikipedia, the free encyclopedia'
    end
  end
 end
end

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [22:26:15] C:1
$ rspec ./spec/features/baidusearch_spec.rb
...

Finished in 5.46 seconds (files took 3.81 seconds to load)
3 examples, 0 failures

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [13:42:41]
$ cucumber
No such file or directory - features. You can use `cucumber --init` to get started.

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [11:24:56] C:2
$ cucumber --init
  create   features
  create   features/step_definitions
  create   features/support
  create   features/support/env.rb

Feature: Search for capybara on baidu
      Scenario: Search for website of baidu
          Given I am on the baidu home page
          When I search for "capybara"
          Then website of search result are returned

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [14:25:16] C:1
$ cucumber
Feature: Search for capybara on baidu

  Scenario: Search for website of baidu        # features/baidu_search_capybara.feature:2
    Given I am on the baidu home page          # features/baidu_search_capybara.feature:3
    When I search for "capybara"               # features/baidu_search_capybara.feature:4
    Then website of search result are returned # features/baidu_search_capybara.feature:5

1 scenario (1 undefined)
3 steps (3 undefined)
0m0.395s

You can implement step definitions for undefined steps with these snippets:

Given(/^I am on the baidu home page$/) do
  pending # Write code here that turns the phrase above into concrete actions
end

When(/^I search for "([^"]*)"$/) do |arg1|
  pending # Write code here that turns the phrase above into concrete actions
end

Then(/^website of search result are returned$/) do
  pending # Write code here that turns the phrase above into concrete actions
end

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [14:25:22]
$ cucumber
Feature: Search for capybara on baidu

  Scenario: Search for website of baidu        # features/baidu_search_capybara.feature:2
    Given I am on the baidu home page          # features/step_definitions/capybara_search_step.rb:1
      TODO (Cucumber::Pending)
      ./features/step_definitions/capybara_search_step.rb:2:in `/^I am on the baidu home page$/'
      features/baidu_search_capybara.feature:3:in `Given I am on the baidu home page'
    When I search for "capybara"               # features/step_definitions/capybara_search_step.rb:5
    Then website of search result are returned # features/step_definitions/capybara_search_step.rb:9

1 scenario (1 pending)
3 steps (2 skipped, 1 pending)
0m0.152s

require 'capybara/cucumber'
Capybara.default_driver = :selenium

Capybara.default_driver = :selenium

# lqi @ CNlqi in ~/work/test/capybara_demo on git:master x [17:13:47] C:2
$ cucumber
rack-test requires a rack application, but none was given (ArgumentError)
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/capybara-2.8.0/lib/capybara/rack_test/driver.rb:17:in `initialize'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/capybara-2.8.0/lib/capybara.rb:509:in `new'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/capybara-2.8.0/lib/capybara.rb:509:in `block in <top (required)>'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/capybara-2.8.0/lib/capybara/session.rb:85:in `call'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/capybara-2.8.0/lib/capybara/session.rb:85:in `driver'
/Users/lqi/work/test/capybara_demo/features/support/env.rb:12:in `<top (required)>'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/rb_support/rb_language.rb:96:in `load'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/rb_support/rb_language.rb:96:in `load_code_file'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:142:in `load_file'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:84:in `block in load_files!'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:83:in `each'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime/support_code.rb:83:in `load_files!'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:253:in `load_step_definitions'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:61:in `run!'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/lib/cucumber/cli/main.rb:32:in `execute!'
/Users/lqi/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/cucumber-2.4.0/bin/cucumber:8:in `<top (required)>'
/Users/lqi/.rbenv/versions/2.2.2/bin/cucumber:23:in `load'
/Users/lqi/.rbenv/versions/2.2.2/bin/cucumber:23:in `<main>'

Given(/^I am on the baidu home page$/) do
  visit 'https://www.baidu.com/'
end

When(/^I search for "([^"]*)"$/) do |search_term|
  fill_in 'kw', :with => search_term
  click_on 'su'
end

Then(/^website of search result are returned$/) do
     page.should have_content 'capybara'

end

visit 'https://www.baidu.com/'

fill_in 'kw', :with => search_term

click_on 'su'

page.should have_content 'capybara'