aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/isolation
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
| * Use RAILS_ISOLATED_ENGINE and fix namespaced generators testsStefan Sprenger2011-06-071-1/+1
| |
| * Don't create full Rails application if RAILS_ISOLATION_COMMAND equals engineStefan Sprenger2011-06-071-1/+1
| |
* | Fix another CIfail :zap: :fire: Deleting RAILS_ENV from ENV doesn't produce ↵Jon Leighton2011-06-061-1/+2
| | | | | | | | the desired result if RACK_ENV is still defined. And in any case it's better to be explicit here, so just set RALS_ENV=development.
* | Solve the RAILS_ENV problem in the railties tests in a more generic wayJon Leighton2011-06-061-0/+6
|/
* Require rubygems (chill out, just for rails internal tests).José Valim2011-05-231-0/+1
|
* No more need rubygems here.Arun Agrawal2011-05-221-2/+0
|
* Add some very simple docs.José Valim2011-04-151-0/+3
|
* Simplify remove_from_config.Emilio Tagua2010-11-191-9/+5
|
* Enable IdentityMap when generating new apps.Emilio Tagua2010-11-191-0/+12
|
* Fix a routing test. Reorganize middleware tests.José Valim2010-10-021-0/+27
|
* Fix running engine_test in isolationPiotr Sarnacki2010-09-191-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Create a deprecation behavior that triggers a notification for deprecation ↵wycats2010-06-291-1/+2
| | | | | | | | | | | | | | | | | notices, and make the behaviors independent of the environment names. * In Rails 2.3 apps being upgraded, you will need to add the deprecation configuration to each of your environments. Failing to do so will result in the same behavior as Rails 2.3, but with an outputted warning to provide information on how to set up the setting. * New Rails 3 applications generate the setting * The notification style will send deprecation notices using ActiveSupport::Notifications. Third-party tools can listen in to these notifications to provide a streamlined view of the deprecation notices occurring in your app. * The payload in the notification is the deprecation warning itself as well as the callstack from the point that triggered the notification.
* Add delete to middleware stack proxy.José Valim2010-06-071-1/+1
|
* Refactor tests by moving all middleware tests to the same place.José Valim2010-04-261-0/+19
|
* moved rails binary to rails gem, so rubygems can find specific versions of ↵Felipe Rodrigues2010-04-121-1/+1
| | | | | | rails [#4382 state:resolved] Signed-off-by: wycats <wycats@gmail.com>
* Rename config.cookie_secret to config.secret_token and pass it as ↵José Valim2010-04-051-1/+1
| | | | configuration in request.env. This is another step forward removing global configuration.
* Deprecated ActionController::Base.session_options= and ↵Carlhuda2010-03-041-1/+1
| | | | ActionController::Base.session_store= in favor of a config.session_store method (which takes params) and a config.cookie_secret variable, which is used in various secret scenarios. The old AC::Base options will continue to work with deprecation warnings.
* Fix Sam Ruby's tests and deprecation warningsCarlhuda2010-03-041-1/+1
|
* Revert "Fix test load paths for those not using bundler"Carlhuda2010-02-231-4/+10
| | | | | | This reverts commit eec2d301d4ce9df9c71c1a5aa63053eb970b6818. This commit broke tests. You cannot have a file called "bundler" on the load path.
* Fix test load paths for those not using bundlerJoshua Peek2010-02-151-10/+4
|
* fix usage examples and more to use new invocationsRomD2010-02-061-1/+1
| | | | Signed-off-by: Carl Lerche <carllerche@mac.com>
* Remove the generated gemfile in railties tests since the rails gemfile is used.Carl Lerche2010-02-021-0/+4
|
* Get rails tests running on bundler 0.9Carl Lerche2010-01-311-19/+7
|
* Add tests for explicit engines.José Valim2010-01-261-0/+21
|
* Rename rails.rb -> rails/all.rb and rails/core.rb -> rails.rbCarl Lerche2009-12-311-1/+1
|
* tests pass with requiring the frameworks in rails.rbCarlhuda2009-12-231-0/+8
|
* Blog -> Blog::Application. Leave the toplevel module up for grabs.Jeremy Kemper2009-12-211-1/+1
|
* test.rb, dev.rb, and production.rb just reopen the Application class; no ↵Carlhuda2009-12-211-0/+7
| | | | more hax required
* Fix bundler environment checkJeremy Kemper2009-11-141-1/+1
|
* Refactor pluginsYehuda Katz + Carl Lerche2009-11-111-0/+28
|
* Fix railties isolated tests if bundler environment doesn't existJoshua Peek2009-11-091-2/+6
|
* Refactored railties' isolation tests to be able to run script/* scripts.Carl Lerche2009-10-211-4/+13
|
* Have all the tests running off a single GemfileYehuda Katz + Carl Lerche2009-10-201-11/+8
|
* Bundle for railties tests tooJeremy Kemper2009-10-191-12/+20
|