The method got extracted out from AR::Base in commit
d916c62c, but the tests never did.

The method itself got extracted out from ActiveRecored::Base in commit
ceb33f84, but the test code never did.

The methods got moved to core.rb in commit
b2c9ce34, but the tests never did.

the time

Spelling correction in Upgrading Guide [ci skip]

Fixes spelling of 'erratta' to 'errata'

[ci skip]

Fix ActionMailer testcase break with mail 2.5.4.

Fix wrong `case_sensitive` in uniqueness validity test

Fix typo in test name and documentation

Missing ending ``` at 14.2 Merging of scopes

http://edgeguides.rubyonrails.org/active_record_querying.html#merging-of-scopes

"normalize_callback_params" doesn't require name param

This reverts commit 8f901dee.

Revert "Changed the CHANGELOG for active_support and improved the doc for inflector method classify"

This reverts commit 8d5fcb69.

Reason: Changelogs are not to be edited in docrails.

[ci skip]

This reverts commit e47c85c6.

Reason: Let's not nodoc without reason.

[ci skip]

This reverts commit 328e876a.

Reason: Let's not nodoc without reason.

[ci skip]

This reverts commit dfb69f2b.

Reason: Let's not nodoc without reason.

[ci skip]

Fixed some typos

Adding notes on PATCH to the upgrade guide. [ci skip]

Add test to counter cache test.rb

Don't autorequire mocha to avoid deprecation warnings

Due to commit 0123c39f, column
topic.unique_replies_count has been added, and these test started to
fail since the tests depends on the topic tables column info.

According to
https://github.com/rails/rails/blob/b601399b72ab56cc01368f02615af99f45d1
4f02/activerecord/lib/active_record/counter_cache.rb#L14, u can pass
more then one association to the `reset_counters` method.

- https://travis-ci.org/rails/rails/jobs/7264822 contains deprecated
  warnings given by Mocha version 0.14
- 632f215d added Mocha 0.14 to Gemfile
- But with the version, require: false was removed
- So Mocha started giving deprecation warnings
- Acc.to Mocha documentation(https://github.com/freerange/mocha#bundler)
  it should not be auto required.

exception are unlikely to pass this assertion, but since the assertions
raise an exception, the original exception is lost.

Bug fix: Evented notification subscribers can handle published events