@@ -3,17 +3,21 @@ Feature: System spec
3
3
System specs are RSpec's wrapper around Rails' own
4
4
[system tests](https://guides.rubyonrails.org/testing.html#system-testing).
5
5
6
- Feature specs are marked by `:type => :system` or if you have set
6
+ > System tests allow you to test user interactions with your application,
7
+ > running tests in either a real or a headless browser. System tests use
8
+ > Capybara under the hood.
9
+ >
10
+ > By default, system tests are run with the Selenium driver, using the
11
+ > Chrome browser, and a screen size of 1400x1400. The next section explains
12
+ > how to change the default settings.
13
+
14
+ System specs are marked by `:type => :system` or if you have set
7
15
`config.infer_spec_type_from_file_location!` by placing them in
8
16
`spec/system`.
9
17
10
- System tests allow you to test user interactions with your application,
11
- running tests in either a real or a headless browser. System tests use
12
- Capybara under the hood.
13
-
14
- By default, system tests are run with the Selenium driver, using the Chrome
15
- browser, and a screen size of 1400x1400. The next section explains how to
16
- change the default settings.
18
+ The Capybara gem is automatically required, so you need that in your
19
+ Gemfile. Configure a webserver (e.g. `Capybara.server = :webrick`) before
20
+ attempting to use system specs.
17
21
18
22
RSpec **does not** use your `ApplicationSystemTestCase` helper. Instead it
19
23
uses the default `driven_by(:selenium)` from Rails. If you want to override
0 commit comments