aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/isolation/abstract_unit.rb
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove deprecated methods at `Kernel`.Rafael Mendonça França2015-01-041-0/+10
| | | | `silence_stderr`, `silence_stream`, `capture` and `quietly`.
* Set the test_order in the basic app as well, see 58e8b48Godfrey Chan2014-11-251-0/+1
| | | | This removes the unwanted deprecation warnings in the tests
* Set the default log_level to info in all testsGodfrey Chan2014-11-251-0/+1
| | | | | | | | | This is a follow-up to 116de07. That change was for two reasons: 1) speed up the tests by reducing the amount of log lines 2) avoid a deprecation warning from a6de6f5. This setting need to be on the basic app too, otherwise the deprecation warning will show up on other unrelated test cases.
* Always default the log_level to :info for RailtiesZachary Scott2014-11-241-0/+1
|
* add a test for #17106Aaron Patterson2014-11-041-0/+9
|
* Define the configuration at Active SupportRafael Mendonça França2014-09-111-0/+1
|
* Set test order in ActiveSupport::TestCase of isolation/abstract_unitRafael Mendonça França2014-09-101-0/+2
|
* Set the test order to be random in the generated appRafael Mendonça França2014-09-101-0/+1
| | | | | | This will avoid the warning in our tests. We delete all the config/environments/ files in the test app so our default code will not work.
* Fix failing railties testsCarlos Antonio da Silva2014-08-191-2/+6
| | | | | | | | | | | | A combination of two commits led into these failures: * The addition of a new active_record config in 24bb8347b6ff0da90059314d9aece7a2c94a272c * The revert of the config to use config.x as options holder in 43073b393d234acd094ac7c220163f4e419d11f5 These tests remove activerecord from the load path, however the configuration is still in the application file, and they blow up.
* Keep quietly and capture undeprecated on your suiteRafael Mendonça França2014-07-151-0/+27
|
* Favor canonical environment variables for secretsschneems2014-01-131-2/+2
| | | | | | | | | Prefixing an environment variable with `RAILS_` should be used when there is otherwise a conflict, such as `RAILS_ENV` or if it is being used for a very Rails specific value. If we remove the prefix of `RAILS_` in the case of `RAILS_SECRET_KEY_BASE` then we can push for a pseudo standard among other frameworks that will accept a common environment key `SECRET_KEY_BASE` to keep your app secure. This is beneficial for containerized deployments such as docker, Heroku, etc. So that the container need to know one less thing about your app (it can just set it no-matter what language or framework you are using). This change also allows the defaults to be consistent with the way the secret key is accessed so `secrets.secret_key_base` is aliased to `SECRET_KEY_BASE` instead of `RAILS_SECRET_KEY_BASE`.
* Revert "Ensure secret_key_base is set for all environments"José Valim2013-12-241-2/+1
| | | | | | A better solution has been pushed to master. This reverts commit 959cfcef7255bba720ce3f15323056533ea7b50a.
* Fix railties tests in masterschneems2013-12-241-1/+2
| | | | | Tests are failing due to missing env var on master https://travis-ci.org/rails/rails/jobs/15930622#L641 This adds an environment variable `ENV['RAILS_SECRET_KEY_BASE']` so these tests will pass.
* Ensure secret_key_base is set for all environmentsJosé Valim2013-12-241-1/+2
|
* Fix build failures related to the new ENV options in ymlJosé Valim2013-12-241-0/+18
|
* Load secret_key_base from tokens.yml, fallback to config.secret_key_baseGuillermo Iguaran2013-12-121-2/+1
|
* Extend basic rendering, test it in railtiesŁukasz Strzałkowski2013-08-251-0/+6
|
* Include AV railtie in railties isolation testsŁukasz Strzałkowski2013-08-251-0/+1
|
* Calls to the application constant have been refactored to usewangjohn2013-06-101-1/+1
| | | | | Rails.application when drawing routes and creating other configurations on the application.
* --no-rc in the railties testsAkira Matsuda2013-02-011-1/+1
| | | | so that the tester's local .railsrc file does not affect the test results
* Introduce ./bin for your app's executables: bin/bundle, bin/rails, bin/rake. ↵Jeremy Kemper2013-01-061-1/+1
| | | | Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'
* Add active_support/testing/autorunRafael Mendonça França2012-12-311-1/+1
| | | | | minitest/autorun load minitest/spec polluting the global namespace with the DSL that we don't want on Rails
* Rename secret_token_key to secret_key_baseSantiago Pastorino2012-11-031-2/+2
|
* Sign cookies using key deriverSantiago Pastorino2012-11-031-2/+2
|
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-141-4/+4
|
* config.activerecord.whitelist_attributes isn't used anymore, remove ↵Guillermo Iguaran2012-09-161-3/+0
| | | | reference from abstract_unit
* Don't use Gemfile in test application in railtiesPiotr Sarnacki2012-08-311-5/+5
| | | | | | | | | | | | | Option to run `bundle install` after generating new appplication was added recently to rails. Since introduction, it contained a subtle bug that caused it to use `Gemfile` from current directory (if it exists) rather than from generated directory. This also accidentaly caused railties tests to work without any problems - after generating test app it just used `Gemfile` from the repository, rather than the one in generated app. After fixing the bug mentioned above, this of course broke. The easiest way to bypass that is to not generate a `Gemfile` for test application - with such setup Bundler will just use first available `Gemfile` in one of the parent directories.
* Set eager load option in "make_basic_app" for railties testsCarlos Antonio da Silva2012-08-211-0/+1
| | | | Avoid output with config option not set when running some tests.
* Allow users to choose when to eager_load the application or not.José Valim2012-08-211-1/+1
| | | | | | | | | | | | | | | | | Previously, the eager load behavior was mostly coupled to config.cache_classes, however this was suboptimal since in some environments a developer may want to cache classes but not necessarily load them all on boot (for example, test env). This pull request also promotes the use of config.eager_load set to true by default in production. In the majority of the cases, this is the behavior you want since it will copy most of your app into memory on boot (which was also the previous behavior). Finally, this fix a long standing Rails bug where it was impossible to access a model in a rake task when Rails was set as thread safe.
* remove some artifacts of dependent_restrict_raises that I missedJon Leighton2012-08-101-1/+0
|
* Remove unnecessary Railties structure now that plugins are goneJosé Valim2012-06-291-11/+5
|
* run railties tests in parallel, default to 2 coresAaron Patterson2012-06-191-2/+0
|
* join any extra args to the tmp pathAaron Patterson2012-06-191-0/+1
|
* expand the tmpdir to the realpath so tests on OS X passAaron Patterson2012-06-191-1/+1
|
* use system tmpdir rather than our ownAaron Patterson2012-06-191-8/+11
|
* Remove useless load path modificationsSantiago Pastorino2012-05-111-3/+2
|
* Remove Declarative module extending, it is already part of AS::TestCaseCarlos Antonio da Silva2012-04-281-2/+0
| | | | Removes method redefined warning.
* Initial queue implementationYehuda Katz2012-04-261-1/+1
|
* Remove default match without specified methodJose and Yehuda2012-04-241-3/+3
| | | | | | | | | | | | | | | | In the current router DSL, using the +match+ DSL method will match all verbs for the path to the specified endpoint. In the vast majority of cases, people are currently using +match+ when they actually mean +get+. This introduces security implications. This commit disallows calling +match+ without an HTTP verb constraint by default. To explicitly match all verbs, this commit also adds a :via => :all option to +match+. Closes #5964
* Fix scaffold controller template, ensure rake scaffold test pass by defaultCarlos Antonio da Silva2012-03-141-1/+6
|
* Remove Active Resource source files from the repositoryPrem Sichanugrist2012-03-131-2/+1
| | | | | | | | | | Dear Active Resource, It's not that I hate you or anything, but you didn't get much attention lately. There're so many alternatives out there, and I think people have made their choice to use them than you. I think it's time for you to have a big rest, peacefully in this Git repository. I will miss you, @sikachu.
* Only add the whitelist_attributes option if ActiveRecord is presentRafael Mendonça França2012-03-041-1/+4
|
* Remove the dependent_restrict_raises configuration if activerecord isRafael Mendonça França2012-02-011-1/+1
| | | | not preset
* require minitest rather than test/unitAaron Patterson2012-01-061-1/+1
|
* convert railties to use AS::TestCaseAaron Patterson2012-01-051-1/+2
|
* Rails::Plugin has goneSantiago Pastorino2012-01-031-14/+0
|
* `rake assets:precompile` loads the application but does not initialize it.José Valim2011-09-241-0/+9
| | | | | | | | | | | | | To the app developer, this means configuration add in config/initializers/* will not be executed. Plugins developers need to special case their initializers that are meant to be run in the assets group by adding :group => :assets. Conflicts: railties/CHANGELOG railties/test/application/assets_test.rb
* Use the proper executable on tests.José Valim2011-09-121-1/+1
|
* Create an :assets group in the Gemfile.José Valim2011-06-211-0/+4
| | | | | | | | | This group is required by default only on development and test (you can change it on config/application.rb). `rake assets:precompile` will automatically add the assets group to Rails.groups (and consequently Bundler.require) and should work transparently.
* Merge pull request #1356 from flippingbits/fix_engine_generatorJosé Valim2011-06-091-1/+1
|\ | | | | Fix engine's generator
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 02:37:11 +0000