1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
Feature: Feature specs
Feature specs are high-level tests meant to exercise slices of functionality
through an application. They should drive the application only via its external
interface, usually web pages.
Feature specs are marked by `type: :feature` or if you have set
`config.infer_spec_type_from_file_location!` by placing them in
`spec/features`.
Feature specs require the [Capybara](https://github.com/teamcapybara/capybara) gem, version 2.13.0 or later.
Refer to the [capybara API documentation](https://rubydoc.info/github/teamcapybara/capybara/master) for more information on the methods and matchers that can be
used in feature specs. Capybara is intended to simulate browser requests with HTTP. It will primarily send HTML content.
The `feature` and `scenario` DSL correspond to `describe` and `it`, respectively.
These methods are simply aliases that allow feature specs to read more as
[customer](http://c2.com/cgi/wiki?CustomerTest) and [acceptance](http://c2.com/cgi/wiki?AcceptanceTest) tests. When capybara is required it sets
`type: :feature` automatically for you.
@capybara
Scenario: Specify creating a Widget by driving the application with capybara
Given a file named "spec/features/widget_management_spec.rb" with:
"""ruby
require "rails_helper"
RSpec.feature "Widget management", type: :feature do
scenario "User creates a new widget" do
visit "/widgets/new"
click_button "Create Widget"
expect(page).to have_text("Widget was successfully created.")
end
end
"""
When I run `rspec spec/features/widget_management_spec.rb`
Then the example should pass
|
