aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/testing.md
diff options
context:
space:
mode:
authorkenta-s <knt01222@gmail.com>2017-03-02 13:03:03 +0900
committerkenta-s <knt01222@gmail.com>2017-02-21 13:48:41 +0900
commit5d3abc06c39a366cc4da3cda1725d92809e2f168 (patch)
treec82e4ede6cc46c0352815fdfd892e8b6b5b8ac5b /guides/source/testing.md
parent6df558f2ab87c410a26cb20373d88317ed4b510b (diff)
downloadrails-5d3abc06c39a366cc4da3cda1725d92809e2f168.tar.gz
rails-5d3abc06c39a366cc4da3cda1725d92809e2f168.tar.bz2
rails-5d3abc06c39a366cc4da3cda1725d92809e2f168.zip
Fix some grammar in docs [ci skip]
Diffstat (limited to 'guides/source/testing.md')
-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 c7897a42a1..113314a5b8 100644
--- a/guides/source/testing.md
+++ b/guides/source/testing.md
@@ -636,11 +636,11 @@ change the default settings.
Rails makes changing the default settings for system test very simple. All
the setup is abstracted away so you can focus on writing your tests.
-When you generate a new application or scaffold, a `application_system_test_case.rb` file
+When you generate a new application or scaffold, an `application_system_test_case.rb` file
is created in the test directory. This is where all the configuration for your
system tests should live.
-If you want to change the default settings you can simple change what the system
+If you want to change the default settings you can simply change what the system
tests are "driven by". Say you want to change the driver from Selenium to
Poltergeist. First add the Poltergeist gem to your Gemfile. Then in your
`application_system_test_case.rb` file do the following:
@@ -685,7 +685,7 @@ This can be helpful for viewing the browser at the point a test failed, or
to view screenshots later for debugging.
Two methods are provided: `take_screenshot` and `take_failed_screenshot`.
-`take_failed_screenshot` is automatically included in `after_teardown` inside
+`take_failed_screenshot` is automatically included in `after_teardown` inside
Rails.
The `take_screenshot` helper method can be included anywhere in your tests to