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

Fx system test example [ci skip]

Browse source 
Since test suffix is automatically granted, it is not necessary to
specify it in generator.
Also, updated the generated file to contents actually generated.
This commit is contained in:
yuuji.yaginuma 2017-03-04 19:09:40 +09:00
parent de17d9e23d
commit 780434d88f
1 changed files with 9 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
guides/source/testing.md
View file

@ -610,9 +610,9 @@ 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.
```bash
$ bin/rails generate system_test users_create_test
$ bin/rails generate system_test users_create
invoke test_unit
create test/system/users_create_test.rb
create test/system/users_creates_test.rb
```
Here's what a freshly-generated system test looks like:
@ -620,10 +620,12 @@ Here's what a freshly-generated system test looks like:
```ruby
require "application_system_test_case"
class UsersCreateTest < ApplicationSystemTestCase
visit users_url
assert_selector "h1", text: "Users"
class UsersCreatesTest < ApplicationSystemTestCase
# test "visiting the index" do
# visit users_creates_url
#
# assert_selector "h1", text: "UsersCreate"
# end
end
```
@ -1436,7 +1438,7 @@ second batch of assertions, we ensure that the email does indeed contain what we
expect. The helper `read_fixture` is used to read in the content from this file.
NOTE: `email.body.to_s` is present when there's only one (HTML or text) part present.
If the mailer provides both, you can test your fixture against specific parts
If the mailer provides both, you can test your fixture against specific parts
with `email.text_part.body.to_s` or `email.html_part.body.to_s`.
Here's the content of the `invite` fixture: