- inbuilt --> built-in
- Remove random spaces from code examples

[ci skip]

- Various grammar fixes
- Added assertions for update controller action tests
- Added user helper tests
- Fix typos

[ci skip]

- Grammar fixes
- Wordsmitting
- Fixed wrong statement about association usage in fixtures
- Changed association name from 'one' to 'first' instead
- More consistent usage of we/our
- Mentions assert_select is below, not already covered in Integration test.

[ci skip]

- Grammar improvements
- Consistent usage of you or we in sentences
- Tests can have zero or more assertions. Its not mandatory to have one.
- Example for assert_send

[ci skip]

I go through the `http://edgeguides.rubyonrails.org/` and found `rake` commands in various files that are in RAILS 5.0 implement by `bin/rails` command. I try to change all that can be directly use `bin/rails …`

This is a pass over the documentation which fills the missing gaps of
`ApplicationRecord`.

[ci skip]

Tiny typo in the testing guide; articules should be articles.

In Rails 5.1 `ActionController::TestCase` will be moved out of Rails
into it's own gem.

Please use `ActionDispatch::IntegrationTest` going foward.

Because this will be moved to a gem I used `# :stopdoc:` instead of
deleting the documentation. This will remove it from the Rails
documentation but still leave the method documented for when we move it
to a gem.

Guides have been updated to use the routing structure used in Integration
and all test examples have been updated to inherit from
`ActionDispatch::IntegrationTest` instead of `ActionController::TestCase.

Fixes #22496

[ci skip]

Since the "Getting Started" guide no longer uses the scaffold generator
we should rewrite references to that in the testing guide.

The functional testing section was quite heavily based on such a
scaffold test. I changed it to use `generate scaffold_controller`
instead so that we can build up on the model foundation we already have.

As discussed in the minitest-spec-rails issue (http://git.io/vlHxx) Rails uses setup/teardown callbacks. Defining `setup` or `teardown` methods vs. blocks will yield inconsistent behavior in the callback chain.

* Fixtures are loaded for all the tests by default (not only model and
  controller tests).
* Fix a few typos and improve the markup at some levels.
* Wrap changes to 80 chars

[ci skip]

[ci skip]

Better reading flow for the information presented in this guide.
The first part is written in a similar fashion as the "Getting Started
Guide" and can be read from start to finish. The second section
introduces the different testing components that Rails provides and
explains how and when to use them.

The guide is still work in progress.

* Add missing `def` and remove useless `do` keywords.
* Move `:nodoc:` in front of the methods' definition so that methods
  under these ones are correctly visible on the API.

[ci skip]

I think people would find it useful to know that you can pass in multiple fixture names to get an array of all the fixtures. I've found this useful in my own app. It looks like there already a test case that supports this feature (https://github.com/rails/rails/blob/master/activerecord/test/cases/fixtures_test.rb#L398), but it's just not documented here.

I look forward to your feedback!

For more details see #20222

Mention that view tests are made in controller tests.

Rails has different naming conventions for the inverse assertion
methods. While minitest uses `refute` we use `_not`. We should have a
table listing the common assertions that you want to use in the Rails
context.

Refs #18305.

rails/rails#18305

* Add conjunction for clarity.
* Add comma between independent clauses: create command, and generation
  of fixtures.