| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
meinac/add_missing_types_into_ar_model_generator_usage"
This reverts commit aaf561d26cf9a879ff40190b625155015c6225da, reversing
changes made to 83776676e54b387fc52081ff31cfd7710bae9e03.
Reason: It is not a good idea to connect to the database on generators
|
|\
| |
| |
| |
| | |
meinac/add_missing_types_into_ar_model_generator_usage
Dynamically show available sql types [ci skip]
|
| |
| |
| |
| | |
Dynamically list available sql data types based on current database adapter.
|
| |
| |
| |
| |
| | |
They're just barren on the site and confure more than guide, instead
rely on the built in --help to guide users.
|
| |
| |
| |
| |
| |
| | |
I'm sorry for causing #24168. I wasn't aware of --no-helper and --no-assets.
So I'm adding them to the help message.
I'm still not sure how to show `--no-test-framework` though.
|
| |
| |
| |
| | |
If `sprockets` is not loaded, `Rails.application.config.assets` is not defined.
|
| |
| |
| |
| | |
We need to use on_load so that plugins will get the same functionality
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test framework should not be autoloaded in production mode. Before
this commit, the testing railtie would extend AS::TestCase. This caused
AS::TestCase to be preloaded regardless of the environment in which we
were running.
This commit just moves the code that adds line filtering support in to
the test command where we actually execute the test runner. That allows
us to maintain the line runner feature but only load the minimal amount
of code we need.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
When the initial evented monitor feature was written, the latest version of listen
was the 3.0.x series. Since then the listen project has moved on to the 3.1.x series.
This patch allows the use of the new versions.
|
| |
| |
| |
| | |
`mongrel` was removed in #26408. But have back accidentally in #26414.
|
| |
| |
| |
| |
| |
| |
| | |
29f0fbd5db643b885665e4a14c7de3bf6c0d9c96 has changed that always call
`Minitest.autorun` in `active_support/testing/autorun`.
Therefore, when used directly `Minitest.run`, tests are performed twice.
|
|\ \
| | |
| | | |
Initial Rails Commands Infrastructure
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Wash out your old! These adhoc scripts are replaced by the new
commands.
|
| | |
| | |
| | |
| | | |
Prescribed some review fixes for myself!
|
| | |
| | |
| | |
| | |
| | | |
Still vulnerable to different file structures. We likely want something
more robust when we tackle in app commands.
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
remove unnecessary `RAILS_ENV` setting
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`RAILS_ENV` is always set in the initialization process of test runner.
https://github.com/rails/rails/blob/9fa07095a35be2d8cb5adcc992b988e73a6d9719/railties/lib/rails/test_unit/minitest_plugin.rb#L74
Therefore, it is not necessary to set in `test_helper`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Makes sure we get support for `Minitest.after_run` hooks and don't
accidentally run tests twice.
Requires overriding minitest `run` to respect the TESTOPTS variable.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Rails test runner supports three ways to run tests: directly, via rake, or ruby.
When Running with Ruby ala `ruby -Itest test/models/post_test.rb` our test file would
be evaluated first, requiring `test_helper` and then `active_support/testing/autorun`
that would then require the test file (which it hadn't been before) thus reevaluating
it. This caused exceptions if using Active Support's declarative syntax.
Fix this by shifting around when we set the how we're run to closer mimick the require
order.
If we're running with `bin/rails test` the test command file is run first and we then
set `run_with_rails_extension`, later we hit `active_support/testing/autorun` and do
nothing — because we've been run elsewhere.
If we at this point haven't set `run_with_rails_extension` we've been running with
`ruby` this whole time and thus we set that.
We should always trigger `Minitest.autorun` as it doesn't hurt to call it twice.
Consolidate the two methods into a single one that better brings out the intent of
why they're there.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Revise the require in the test command to use `active_support/testing/autorun`
and spare us the minitest spec syntax as detailed in 5da4d51.
Also move the require to the top of the file for consistency with the rest of
Rails' requires across the project.
|
|\ \ \
| | | |
| | | | |
AS => Active Support [ci skip]
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
support minitest after_run
|
| | | |
|
| | |
| | |
| | |
| | | |
see https://github.com/seattlerb/minitest/blob/f9605387e4af7d657921a83aaf0ae364f6d26a57/lib/minitest.rb#L51-L65
|
| | | |
|
|\ \ \
| | | |
| | | | |
use rails command in restart task test
|
| | | | |
|
|/ / / |
|
|/ /
| |
| |
| |
| |
| | |
assert [1, 3].includes?(2) fails with unhelpful "Asserting failed" message
assert_includes [1, 3], 2 fails with "Expected [1, 3] to include 2" which makes it easier to debug and more obvious what went wrong
|
|\ \
| | |
| | | |
remove useless `gemfile` option
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rails application for test creates with `--skip-gemfile` option.
https://github.com/rails/rails/blob/master/railties/test/isolation/abstract_unit.rb#L333
Therefore, regardless of the option, Gemfile is not created.
|
|\ \ \
| | | |
| | | | |
Move comment about disconnecting pool close to comment about preload
|
| | | |
| | | |
| | | |
| | | | |
- These two comments are connected to each other so kept them back to back.
|
|/ / /
| | |
| | |
| | | |
Follow up to 92703a9ea5d8b96f30e0b706b801c9185ef14f0e
|
| | |
| | |
| | |
| | | |
Master based applications should be pointing to master
|
|\ \ \
| | | |
| | | | |
Disconnects all connections in the pool before forking.
|
| | | |
| | | |
| | | |
| | | | |
See discussion in https://github.com/puma/puma/issues/1001
|
| |/ /
|/| |
| | |
| | | |
Lacks some proper creds to the homies who went the... distance ;)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, `bin/setup` test uses Gemfile of Rails. But this Gemfile is not a
file to be used in Rails application.
Add a Gemfile to Rails application that is created for test, it has been
modified to use the Gemfile.
|