- 24 4月, 2016 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
- Followup of https://github.com/rails/rails/pull/24709.
-
- 05 3月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
Follow up to #24050.
-
- 04 3月, 2016 2 次提交
-
-
由 Mohit Natoo 提交于
-
由 Mohit Natoo 提交于
-
- 28 2月, 2016 1 次提交
-
-
由 yuuji.yaginuma 提交于
In order to eliminate the dependecy of CoffeeScript.
-
- 26 2月, 2016 1 次提交
-
-
由 Ryo Hashimoto 提交于
(e.g. `rails:update` and `rails:template` tasks is renamed to `app:update` and `app:template`.)
-
- 25 2月, 2016 1 次提交
-
-
由 Jon Moss 提交于
This also marks Action Cable routes as internal to Rails.
-
- 11 2月, 2016 1 次提交
-
-
由 Abhishek Jain 提交于
-
- 06 2月, 2016 1 次提交
-
-
由 yuuji.yaginuma 提交于
It has been changed to require `belongs_to` by default in Rails 5. Therefore in order to pass the controller test, have association of set to fixtures. Fixes #23384
-
- 03 2月, 2016 1 次提交
-
-
由 yuuji.yaginuma 提交于
For other task has become to use the rails command at doc and test, I think that routes task also it is better to use the rails command.
-
- 02 2月, 2016 1 次提交
-
-
由 Vipul A M 提交于
Add two options: `-c` and `-g`. `-g` option returns the urls name, verb and path fields that match the pattern. `-c` option returns the urls for specific controller. Fixes #18902, and Fixes #20420 [Anton Davydov & Vipul A M]
-
- 24 1月, 2016 1 次提交
-
-
由 Vipul A M 提交于
Be consistent in testing outputs from railties test and use /bin/rails everywhere(the default behaviour now) instead of mix of /bin/rake /bin/rails everywhere [Ryo Hashimoto & Vipul A M]
-
- 11 1月, 2016 1 次提交
-
-
由 yuuji.yaginuma 提交于
This removes the following warnings. ``` test/application/rake_test.rb:33: warning: ambiguous first argument; put parentheses or a space even after `/' operator test/application/rake_test.rb:43: warning: ambiguous first argument; put parentheses or a space even after `/' operator ```
-
- 08 1月, 2016 1 次提交
-
-
由 schneems 提交于
This PR introduces a key/value type store to Active Record that can be used for storing internal values. It is an alternative implementation to #21237 cc @sgrif @matthewd. It is possible to run your tests against your production database by accident right now. While infrequently, but as an anecdotal data point, Heroku receives a non-trivial number of requests for a database restore due to this happening. In these cases the loss can be large. To prevent against running tests against production we can store the "environment" version that was used when migrating the database in a new internal table. Before executing tests we can see if the database is a listed in `protected_environments` and abort. There is a manual escape valve to force this check from happening with environment variable `DISABLE_DATABASE_ENVIRONMENT_CHECK=1`.
-
- 18 12月, 2015 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 16 12月, 2015 2 次提交
-
-
由 Genadi Samokovarov 提交于
It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present.
-
由 eileencodes 提交于
Running railties generated app tests in development env can cause unintended consequences. The environments are different and tests aren't meant to be run in development mode. The changes to the generator exposed this issue where the random test order in the generated apps could cause problems when those tests are run in development mode. Particularly we saw failures in `railties/test/application/rake_test.rb` generated apps that used the scaffold to create applications and then run the migration and immediately run the tests. The error we saw was `ActiveRecord::RecordNotFound: Couldn't find User with 'id'=980190962` and seemed to only occur if the destroy test ran first. I'm not entirely sure _why_ this causes that error to be thrown but I believe it is related to the environments being different.
-
- 18 9月, 2015 1 次提交
-
-
由 Akira Matsuda 提交于
-
- 30 6月, 2015 1 次提交
-
-
由 Yves Senn 提交于
We recommend using the `bin/` executables in our docs and guides. Let's make sure that our tests execute the same code path.
-
- 12 6月, 2015 3 次提交
-
-
由 Sean Griffin 提交于
This looks to be just out of sync tests
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 30 5月, 2015 1 次提交
-
-
由 Yoong Kang Lim 提交于
See #20299.
-
- 02 5月, 2015 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
- Based on DHH's suggestion about deprecating `assigns` in https://github.com/rails/rails/pull/18305#issuecomment-68605166.
-
- 24 3月, 2015 1 次提交
-
-
由 Jeroen van Baarsen 提交于
* Jobs generated now inherent from ApplicationJob * ApplicationJob inherents from ActiveJob::Base * Added entry to changelog Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 22 2月, 2015 1 次提交
-
-
由 Josef Šimánek 提交于
Deprecate `required` option in favor of `optional` for belongs_to.
-
- 08 1月, 2015 1 次提交
-
-
由 Dieter Komendera 提交于
`rake test:load_structure` already uses `SCHEMA` and there's no need to maintain two different env vars.
-
- 08 3月, 2014 1 次提交
-
-
由 Robin Dupret 提交于
Templates could rely on irregular inflections or external libraries for instance so we should load the application's initializers when running the rails:template task. The introducing commit of this feature is f7f11361 ; the initializers have never been loaded invoking this task. Fixes #12133.
-
- 02 1月, 2014 1 次提交
-
-
由 Jon Leighton 提交于
* Move check from generated helper to test_help.rb, so that all applications can benefit * Rather than just raising when the test schema has pending migrations, try to load in the schema and only raise if there are pending migrations afterwards * Opt out of the check by setting config.active_record.maintain_test_schema = false * Deprecate db:test:* tasks. The test helper is now fully responsible for maintaining the test schema, so we don't need rake tasks for this. This is also a speed improvement since we're no longer reloading the test database on every call to "rake test".
-
- 15 12月, 2013 1 次提交
-
-
由 Arthur Neves 提交于
-
- 22 11月, 2013 2 次提交
-
-
由 Arun Agrawal 提交于
Broken by 6701b4cf
-
由 Sıtkı Bağdat 提交于
This commit fixes formatting issue for `rake routes` task, when a section is shorter than a header.
-
- 01 11月, 2013 1 次提交
-
-
由 Arun Agrawal 提交于
Same as 4d4ff531
-
- 11 7月, 2013 1 次提交
-
-
由 Paul Nikitochkin 提交于
Closes #11381
-
- 24 6月, 2013 1 次提交
-
-
由 wangjohn 提交于
The `rake test:recent` and `rake test:uncommitted` tasks were deprecated and are now being removed.
-
- 11 6月, 2013 1 次提交
-
-
由 wangjohn 提交于
Rails.application when drawing routes and creating other configurations on the application.
-
- 04 6月, 2013 1 次提交
-
-
由 wangjohn 提交于
more agnostic Rails.application syntax. This means tests will be more portable, and won't rely on the existence of a particular subclass.
-
- 01 6月, 2013 1 次提交
-
-
由 wangjohn 提交于
particular controller to search for in rake routes.
-
- 30 5月, 2013 1 次提交
-
-
由 wangjohn 提交于
environment works correctly.
-
- 07 5月, 2013 1 次提交
-
-
由 Ryan Davis 提交于
+ Namespace changes, overhaul of runners. + Internal ivar name changes - Removed a logger globally applied to tests that spew everywhere?!? + Override Minitest#__run to sort tests by name. + Reworked testing isolation to work with the new cleaner architecture. - Removed a bunch of tests that just test minitest straight up. I think these changes were all merged to minitest 4 a long time ago. - Minor report output differences.
-