aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorRobin Dupret <robin.dupret@gmail.com>2017-06-06 17:31:24 +0200
committerRobin Dupret <robin.dupret@gmail.com>2017-06-06 17:36:02 +0200
commit2759a53a54fc7d834141adca22f3e76d928a7064 (patch)
tree8ec0e004942038540461405b54f28c879ffe80f0 /guides
parent88201e41ea408c3def3eab703d68fabdba9a4146 (diff)
downloadrails-2759a53a54fc7d834141adca22f3e76d928a7064.tar.gz
rails-2759a53a54fc7d834141adca22f3e76d928a7064.tar.bz2
rails-2759a53a54fc7d834141adca22f3e76d928a7064.zip
Tiny documentation fixes [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/testing.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/guides/source/testing.md b/guides/source/testing.md
index 565f40ed37..7abf3af187 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -602,8 +602,8 @@ Model tests don't have their own superclass like `ActionMailer::TestCase` instea
System Testing
--------------
-System tests allows test user interactions with your application, running tests
-in either a real or a headless browser. System tests uses Capybara as base.
+System tests allow you to test user interactions with your application, running tests
+in either a real or a headless browser. System tests uses Capybara under the hood.
For creating Rails system tests, you use the `test/system` directory in your
application. Rails provides a generator to create a system test skeleton for you.
@@ -670,7 +670,7 @@ end
```
If your Capybara configuration requires more setup than provided by Rails, this
-additional configuration could be added into `application_system_test_case.rb`
+additional configuration could be added into the `application_system_test_case.rb`
file.
Please see [Capybara's documentation](https://github.com/teamcapybara/capybara#setup)