| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[ci skip]
|
|
|
|
|
|
| |
Lots of grammar, etc fixes.
[ci skip]
|
|
|
|
|
|
| |
Lots of grammar, etc fixes.
[ci skip]
|
| |
|
|\
| |
| | |
Add link to API documentation [ci skip]
|
| |
| |
| | |
Add a link to http://api.rubyonrails.org/classes/ActionController.html in the beginning of an article.
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| |
| | |
Small change to improve the readability in section 2.3 of the testing
guide.
|
| |
| |
| |
| | |
See the rationale in the comment found in the patch.
|
|\ \
| | |
| | | |
Improve foreign key description in guides
|
| | | |
|
| | |
| | |
| | |
| | | |
That option was removed in 0a683085b1db435b7371350b2799a0f248cd717a
|
|\ \ \
| | | |
| | | | |
Avoid running system tests by default
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These tests may be expansive so let's only allow users to run them
through `bin/rails test:system` or by passing a path to the `test`
command.
The same applies for `bin/rake test`.
Refs #28109.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| | | |
| | | | |
Fx system test example [ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since test suffix is automatically granted, it is not necessary to
specify it in generator.
Also, updated the generated file to contents actually generated.
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
passing unique parameter to belongs_to wrongly
|
| | | |
| | | |
| | | | |
passing `unique` parameter to belongs_to not right,
|
|/ / /
| | |
| | | |
[ci skip]
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The current Basic Test Case example has the following assertion
```
assert_equal read_fixture('invite').join, email.body.to_s
```
email.body.to_s returns an empty string if both HTML and text templates
exist for a given mailer. This commit adds a note to section 11.2.2
explaining this and also suggests using email.text_part.body.to_s
and email.html_part.body.to_s as alternatives.
|
| | | |
|
| | |
| | |
| | |
| | | |
Follow up to ea9566f6cd1b4d3f0d8a5f03283b49423b89044d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since using a `ActiveSupport::Deprecation::DeprecatedConstantProxy`
would prevent people from inheriting this class and extending it
from the `ActiveSupport::HashWithIndifferentAccess` one would break
the ancestors chain, that's the best option we have here.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
As the specified command is `rails g system_test articles`, the generated class name
is `ArticlesTest`, not `UsersTest`
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
There were some grammar issues and incorrect information in the system
tests documentation.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This renames the system test helper file to be application system test
case to match what the rest of Rails does. In the future we should
consider changing the test_helper to match.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Move system tests back into Action Pack
* Rename `ActionSystemTest` to `ActionDispatch::SystemTestCase`
* Remove private base module and only make file for public
`SystemTestCase` class, name private module `SystemTesting`
* Rename `ActionSystemTestCase` to `ApplicationSystemTestCase`
* Update corresponding documentation and guides
* Delete old `ActionSystemTest` files
|
| | |
| | |
| | |
| | |
| | | |
Update the documentation after rewriting a majority of the functionality
for system testing.
|
| | |
| | |
| | |
| | |
| | | |
This adds the required guides for how to write and use system tests in
your application.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Remove deprecate passing string to `:if` and `:unless` conditional options [ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[ci skip]
Follow up to #27608
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change Rails engine guide to references a maintained project
Thredded instead of the abandoned project Forem. I chose
Thredded as Forem's closing note (below) suggests the choice.
https://github.com/rubysherpas/forem/blob/rails4/README.md
|
|/ / / |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit is not precisely atomic, but the changes have evolved, summary:
* The ENV-based interface has been moved upwards, the generator has now a conventional
initializer.
* RAILS_VERSION is now assumed to be a Git tag. A blank RAILS_VERSION means edge guides.
* In consequence, the EDGE env variable is gone.
* The "local" version is also gone, the current SHA1 is computed for edge guides.
* Assumes guides are generated from a repo checkout (time ago users could
generate them from gems.)
* The WARNINGS flag is gone in consequence, you cannot disable warnings.
* The `api_link` Markdown helper is fixed.
* Docs about usage have one single place: rake guides:help.
* Links in guides have been revised.
|
| | |
| | |
| | |
| | | |
Switch extension 👉 format as it's more apt here.
|
|\ \ \
| | | |
| | | | |
Get TODO done in `render_test`
|
| |/ / |
|