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

some typos and rephrasing in system test guide [ci skip]

Browse source
This commit is contained in:
Cesar Carruitero 2017-05-16 00:13:01 -05:00
parent 661f537b15
commit 31fe0ec28d
1 changed files with 8 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
guides/source/testing.md
View file

@ -600,11 +600,8 @@ Model tests don't have their own superclass like `ActionMailer::TestCase` instea
System Testing
--------------
System tests are full-browser tests that can be used to test your application's
JavaScript and user experience. System tests use Capybara as a base.
System tests allow for running tests in either a real browser or a headless
driver for testing full user interactions with your application.
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.
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.
@ -669,8 +666,9 @@ class ApplicationSystemTestCase < ActionDispatch::SystemTestCase
end
```
If your Capybara configuration requires more setup than provided by Rails, all
of that configuration can be put into the `application_system_test_case.rb` file.
If your Capybara configuration requires more setup than provided by Rails, this
additional configuration could be added into `application_system_test_case.rb`
file.
Please see [Capybara's documentation](https://github.com/teamcapybara/capybara#setup)
for additional settings.
@ -693,9 +691,9 @@ take a screenshot of the browser.
Now we're going to add a system test to our blog application. We'll demonstrate
writing a system test by visiting the index page and creating a new blog article.
If you used the scaffold generator, a system test skeleton is automatically
created for you. If you did not use the generator start by creating a system
test skeleton.
If you used the scaffold generator, a system test skeleton was automatically
created for you. If you didn't use the scaffold generator, start by creating a
system test skeleton.
```bash
$ bin/rails generate system_test articles