mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
[ci skip] Minor documentation fixes for consistency
This commit is contained in:
parent
0771bd3ee8
commit
70192cec42
4 changed files with 4 additions and 4 deletions
|
@ -9639,7 +9639,7 @@ jQuery.fn.extend( {
|
||||||
// 2) For the hidden or detached element
|
// 2) For the hidden or detached element
|
||||||
// 3) For body or html element, i.e. in case of the html node - it will return itself
|
// 3) For body or html element, i.e. in case of the html node - it will return itself
|
||||||
//
|
//
|
||||||
// but those exceptions were never presented as a real life use-cases
|
// but those exceptions were never presented as a real life use cases
|
||||||
// and might be considered as more preferable results.
|
// and might be considered as more preferable results.
|
||||||
//
|
//
|
||||||
// This logic, however, is not guaranteed and can change at any point in the future
|
// This logic, however, is not guaranteed and can change at any point in the future
|
||||||
|
|
|
@ -798,7 +798,7 @@ to load a file using the current [loading mechanism](#loading-mechanism), and
|
||||||
keeping track of constants defined in that file as if they were autoloaded to
|
keeping track of constants defined in that file as if they were autoloaded to
|
||||||
have them reloaded as needed.
|
have them reloaded as needed.
|
||||||
|
|
||||||
`require_dependency` is rarely needed, but see a couple of use-cases in
|
`require_dependency` is rarely needed, but see a couple of use cases in
|
||||||
[Autoloading and STI](#autoloading-and-sti) and [When Constants aren't
|
[Autoloading and STI](#autoloading-and-sti) and [When Constants aren't
|
||||||
Triggered](#when-constants-aren-t-missed).
|
Triggered](#when-constants-aren-t-missed).
|
||||||
|
|
||||||
|
|
|
@ -1012,7 +1012,7 @@ Finally we can assert that our response was successful and our new article is re
|
||||||
|
|
||||||
#### Taking it further
|
#### Taking it further
|
||||||
|
|
||||||
We were able to successfully test a very small workflow for visiting our blog and creating a new article. If we wanted to take this further we could add tests for commenting, removing articles, or editing comments. Integration tests are a great place to experiment with all kinds of use-cases for our applications.
|
We were able to successfully test a very small workflow for visiting our blog and creating a new article. If we wanted to take this further we could add tests for commenting, removing articles, or editing comments. Integration tests are a great place to experiment with all kinds of use cases for our applications.
|
||||||
|
|
||||||
|
|
||||||
Functional Tests for Your Controllers
|
Functional Tests for Your Controllers
|
||||||
|
|
|
@ -234,7 +234,7 @@ module ApplicationTests
|
||||||
|
|
||||||
# TODO: would be nice if we could detect the schema change automatically.
|
# TODO: would be nice if we could detect the schema change automatically.
|
||||||
# For now, the user has to synchronize the schema manually.
|
# For now, the user has to synchronize the schema manually.
|
||||||
# This test-case serves as a reminder for this use-case.
|
# This test case serves as a reminder for this use case.
|
||||||
test "manually synchronize test schema after rollback" do
|
test "manually synchronize test schema after rollback" do
|
||||||
output = rails("generate", "model", "user", "name:string")
|
output = rails("generate", "model", "user", "name:string")
|
||||||
version = output.match(/(\d+)_create_users\.rb/)[1]
|
version = output.match(/(\d+)_create_users\.rb/)[1]
|
||||||
|
|
Loading…
Reference in a new issue