kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Fix some grammar in docs [ci skip]

Browse source
This commit is contained in:
kenta-s 2017-03-02 13:03:03 +09:00
parent 6df558f2ab
commit 5d3abc06c3
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
actionpack/lib/action_dispatch/system_test_case.rb
View file

@ -36,7 +36,7 @@ module ActionDispatch
# end
# end
#
# When generating an application or scaffold a +application_system_test_case.rb+
# When generating an application or scaffold, an +application_system_test_case.rb+
# file will also be generated containing the base class for system testing.
# This is where you can change the driver, add Capybara settings, and other
# configuration for your system tests.

6
guides/source/testing.md
View file

@ -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