Joshua Peek d859402696 Use Rails.initialize! where we just want to run the initializers and aren't concerned about the config		2009-10-16 18:58:35 -05:00
..
application	Use Rails.initialize! where we just want to run the initializers and aren't concerned about the config	2009-10-16 18:58:35 -05:00
fixtures
generators	Deprecate RAILS_ROOT in favor of Rails.root (which proxies to the application's object root)	2009-10-16 12:51:02 -07:00
initializer	Use Rails.initialize! where we just want to run the initializers and aren't concerned about the config	2009-10-16 18:58:35 -05:00
isolation	Make the railties tests pass	2009-10-16 16:31:05 -07:00
mocks
vendor/gems
abstract_unit.rb	Deprecate RAILS_ROOT in favor of Rails.root (which proxies to the application's object root)	2009-10-16 12:51:02 -07:00
backtrace_cleaner_test.rb	Deprecate RAILS_ROOT in favor of Rails.root (which proxies to the application's object root)	2009-10-16 12:51:02 -07:00
gem_dependency_test.rb
generators_test.rb
initializable_test.rb	Add a test that ensures that Rails::Initializable can be used with modules	2009-10-08 12:31:09 -07:00
metal_test.rb
paths_test.rb	Make rails configuration's path object's root lazy	2009-10-14 11:18:45 -07:00
plugin_loader_test.rb	Finish porting over the initializers to the app object and fix all the tests	2009-10-08 18:12:28 -07:00
plugin_locator_test.rb	Finish porting over the initializers to the app object and fix all the tests	2009-10-08 18:12:28 -07:00
plugin_test.rb	Finish porting over the initializers to the app object and fix all the tests	2009-10-08 18:12:28 -07:00
plugin_test_helper.rb
rails_info_controller_test.rb
rails_info_test.rb