Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

Setting fixtures automatically for integration tests is a bit harder …

…-- will have to wait until the test superclass reform is implemented

git-svn-id: 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
  • Loading branch information...
commit 23e24c5996c90e072b66a616ee0cbe066dd5c1a2 1 parent 87b7b5b
@dhh dhh authored
2  activerecord/lib/active_record/fixtures.rb
@@ -490,10 +490,12 @@ def self.require_fixture_classes(table_names=nil)
def self.setup_fixture_accessors(table_names=nil)
(table_names || fixture_table_names).each do |table_name|
table_name ='.','_')
define_method(table_name) do |fixture, *optionals|
force_reload = optionals.shift
@fixture_cache[table_name] ||=
@fixture_cache[table_name][fixture] = nil if force_reload
if @loaded_fixtures[table_name][fixture.to_s]
@fixture_cache[table_name][fixture] ||= @loaded_fixtures[table_name][fixture.to_s].find
3  railties/helpers/test_helper.rb
@@ -27,6 +27,9 @@ class Test::Unit::TestCase
# Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
# If you need to control the loading order (due to foreign key constraints etc), you'll
# need to change this line to explicitly name the order you desire.
+ #
+ # Note: You'll currently still have to declare fixtures explicitly in integration tests
+ # -- they do not yet inherent this setting
fixtures :all
# Add more helper methods to be used by all tests here...
Please sign in to comment.
Something went wrong with that request. Please try again.