aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test
Commit message (Collapse)AuthorAgeFilesLines
* Add skip_eager_load!, skip_autoload! and friends to path objects.José Valim2010-07-171-2/+22
|
* Makes test use the new config.action_view.javascript_expansions[:defaults] ↵Santiago Pastorino2010-07-171-1/+1
| | | | initialization syntax
* Adds application.js when app is generated with -J and clear ↵Santiago Pastorino2010-07-171-1/+6
| | | | javascript_expansions[:defaults]
* Just add connection management middleware if running in a concurrent ↵José Valim2010-07-122-2/+11
| | | | environment.
* Add a test to ensure url helpers are not action methods in ActionMailer.José Valim2010-07-071-0/+19
|
* Fix indentJeremy Kemper2010-07-021-1/+1
|
* Avoid calls to Rails::Application since this is not the official API.José Valim2010-07-014-5/+5
| | | | Your application should *always* reference your application const (as Blog::Application) and Rails.application should be used just internally.
* Create a deprecation behavior that triggers a notification for deprecation ↵wycats2010-06-292-1/+3
| | | | | | | | | | | | | | | | | 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.
* Push a failing test for issues [#4994] and [#5003].José Valim2010-06-291-1/+14
|
* A few changes were done in this commit:José Valim2010-06-284-72/+63
| | | | | | * Added :autoload to engines path API and redefine usage to be in sync with 6f83a5036d8a9c3f8ed7; * Do not autoload code in *lib* for applications (now you need to explicitly require them). This makes an application behave closer to an engine (code in lib is still autoloaded for plugins); * Always autoload code in app/ for engines and plugins. This makes engines behave closer to an application and should allow us to get rid of the unloadable hack required when controllers inside engines inherit from ApplicationController;
* adding missing assertion and fixing the testNeeraj Singh2010-06-241-2/+4
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* fixing test by replacing assert with assert_equalNeeraj Singh2010-06-241-1/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Remove the --singeleton option from scaffold generator.Prem Sichanugrist2010-06-242-22/+0
| | | | | | | | It turned out to be that scaffold for singeleton resource will always depend on another model, and it's not possible at the moment to make the application tests pass after generate the singeleton scafold. So, it would be better to remove it for now and probably provide another generator, such as singeleton_scaffold, in which also require the depended model name. [#4863 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* adding middleware test for RAILS_CACHENeeraj Singh2010-06-241-0/+11
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Remove obsolete test case, since we have move Rails::LogSubscriber to ↵Prem Sichanugrist2010-06-241-9/+0
| | | | | | ActiveSupport::LogSubscriber in [6788db824ab732b13493a9d702dd8fb89fa153c8] [#4816 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* AS::Isolation functional on Windows/JRuby.Nick Sieger2010-06-241-2/+0
| | | | | | Doesn't make up for the fact that it's slooooooooow, though. Signed-off-by: wycats <wycats@gmail.com>
* Move Rails::LogSubscriber to ActiveSupport::LogSubscriber, allowing ↵José Valim2010-06-241-123/+0
| | | | frameworks like ActiveRecord and ActiveResource to log outsude Rails::Application [#4816 state:resolved]
* Remove run_initializers from class methods.José Valim2010-06-241-25/+14
|
* Speed up boot by tsorting as infrequently as possibleJeremy Kemper2010-06-241-1/+1
|
* Array#sample now exists, so test for #forty_two insteadJeremy Kemper2010-06-241-1/+1
|
* renames load_(once_)paths to autoload_(once_)paths in dependencies and configXavier Noria2010-06-241-3/+3
|
* Patch for Namespace problem in Scaffold. [#4763 state:resolved]Mohammed Siddick.E2010-06-231-0/+106
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Added 4 tests for Rails Runner. 2 failing tests for $0 and $PROGRAM_NAME ↵rohit2010-06-221-0/+49
| | | | | | [#2244 state:open] Signed-off-by: José Valim <jose.valim@gmail.com>
* Revert "files in the lib directory are no longer autoloaded"Xavier Noria2010-06-211-3/+1
| | | | | | | This patch is not consistent since it leaves similar directories in load_paths, needs more thought. This reverts commit b5fe014fdcc285f3bcb8779c4f7cfbc5a820856f.
* files in the lib directory are no longer autoloadedXavier Noria2010-06-211-1/+3
| | | | | | | | | | | Conceptually, the lib directory is closer 3rd party libraries than to the application itself. Thus, Rails adds it to Ruby's load path ($LOAD_PATH, $:) but it is no longer included in dependencies' load paths. To enable autoloading back put this in your config/application.rb config.load_paths += %W( #{config.root}/lib )
* I18n.reload! is only called if any of the locale files actually changed.José Valim2010-06-202-108/+114
|
* Add test for migration generator with name not starting with add or remove. ↵rohit2010-06-201-0/+15
| | | | | | [#4835 state:committed] Signed-off-by: José Valim <jose.valim@gmail.com>
* Make polymorphic_url and scaffolding work with uncountable resources [#3930 ↵Andrew White2010-06-201-0/+10
| | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Clear DescendantsTracker on each request.José Valim2010-06-194-35/+75
|
* Add a failing test for ticket #4874José Valim2010-06-171-0/+14
|
* edit pass: the names of Rails components have a space, ie, "Active Record", ↵Xavier Noria2010-06-141-1/+1
| | | | not "ActiveRecord"
* Tidy up generators based on latest change on AM.José Valim2010-06-131-2/+2
|
* Test create mailers folder when starting a new appDamien Mathieu2010-06-121-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* abort generation/booting on Ruby 1.9.1Xavier Noria2010-06-101-1/+3
|
* layout 'application' is not anymore on application_controllerSantiago Pastorino2010-06-101-2/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* detect being inside a rails application even from a subdirectoryChad Fowler2010-06-101-0/+22
| | | | Signed-off-by: David Heinemeier Hansson <david@loudthinking.com>
* Rails::Generators::GeneratedAttribute: tests, cleanups and a bugfix [#4631 ↵Jeff Kreeftmeijer2010-06-101-10/+81
| | | | | | state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Ensure show exceptions middleware properly filters backtrace before logging.José Valim2010-06-091-0/+20
|
* Should call configure! to initiliaze the applicationSantiago Pastorino2010-06-091-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Fix generator test broken when rails new was added.José Valim2010-06-081-3/+1
|
* Add delete to middleware stack proxy.José Valim2010-06-072-1/+7
|
* removes Array#random_element and backports Array#sample from Ruby 1.9, ↵Xavier Noria2010-06-051-2/+2
| | | | thanks to Marc-Andre Lafortune
* Still copy application configuration to generator even if they are required ↵José Valim2010-06-021-2/+5
| | | | earlier. Also tidy up the guide a little bit.
* Add lib to load paths when application is inherited to be able to load lib ↵José Valim2010-06-021-0/+17
| | | | code during configuration.
* Remove the laziness from the middleware stack.José Valim2010-05-293-3/+3
|
* Removing Metal from Rails 3. wycats2010-05-295-129/+0
| | | | | | | | | | | | | | | | | | | | If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
* Fix a bug where I18n fallbacks modules where not included in the proper ↵José Valim2010-05-231-7/+10
| | | | backend if it was set through config.i18n.backend.
* Fix typo on rackup test (ht: pleax)José Valim2010-05-201-1/+1
|
* Final iteration of use better testing methodsNeeraj Singh2010-05-191-2/+2
| | | | | | [#4652 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* Simplify cookie_store by simply relying on cookies.signed.José Valim2010-05-182-3/+6
|