I'm working on upgrading from attachment_fu to carrierwave, since attachment_fu is broken in rails 3.
None of the tests are able to run, because we have invalid fixtures that were using the syntax from attachment_fu for attachment files.
For example, we have a Post model that has one PostAttachment. Here's what the data in the PostAttachment fixture looks like:
a_image:
post_id: 1
attachment_file: <%= Rails.root>/test/files/test.png
And this is the error I'm getting:
ActiveRecord::StatementInvalid: PGError: ERROR: column "attachment_file" of relation "post_attachments" does not exist
LINE 1: INSERT INTO "post_attachments" ("post_id", "attachment_file"...
attachment_file
would have been picked up by attachment_fu, and it would have taken care of all the processing to create the attachment_fu attachment for the model.
Is there a way to have image attachments in the fixtures, but with using CarrierWave instead?
The only way I've managed to get this to work is to use a storage provider specifically for testing that doesn't actually save/read files.
In your config/initializers/carrier_wave.rb
Add a NullStorage class that implements the minimum interface for a storage provider.
# NullStorage provider for CarrierWave for use in tests. Doesn't actually
# upload or store files but allows test to pass as if files were stored and
# the use of fixtures.
class NullStorage
attr_reader :uploader
def initialize(uploader)
@uploader = uploader
end
def identifier
uploader.filename
end
def store!(_file)
true
end
def retrieve!(_identifier)
true
end
end
Then when initializing CarrierWave add a clause for the test environment, e.g.,
if Rails.env.test?
config.storage NullStorage
end
Here is a gist of my complete carrier_wave.rb for reference. It also includes how to setup S3 for uploads in staging/production and local storage for development so you can see how to configure CarrierWave in context.
Once CarrierWave is configured you can simply put any string in the fixtures column to simulate an uploaded file.