Sha256: 4a671e91b51d80647b29e57d9efe0edc01bf6231650209d737fa0ac89b25c821
Contents?: true
Size: 1.44 KB
Versions: 20
Compression:
Stored size: 1.44 KB
Contents
Feature: uploader with file storage
In order to be awesome
As a developer using CarrierWave
I want to upload files to the filesystem
Background:
Given an uploader class that uses the 'grid_fs' storage
And an instance of that class
Scenario: store a file
When I store the file 'fixtures/bork.txt'
Then the contents of the file should be 'this is a file'
Scenario: store two files in succession
When I store the file 'fixtures/bork.txt'
Then the contents of the file should be 'this is a file'
When I store the file 'fixtures/monkey.txt'
Then the contents of the file should be 'this is another file'
Scenario: cache a file and then store it
When I cache the file 'fixtures/bork.txt'
Then there should be a file called 'bork.txt' somewhere in a subdirectory of 'public/uploads/tmp'
And the file called 'bork.txt' in a subdirectory of 'public/uploads/tmp' should be identical to the file at 'fixtures/bork.txt'
And there should not be a file at 'public/uploads/bork.txt'
When I store the file
Then the contents of the file should be 'this is a file'
Scenario: retrieving a file from cache then storing
Given the file 'fixtures/bork.txt' is cached file at 'public/uploads/tmp/20090212-2343-8336-0348/bork.txt'
When I retrieve the cache name '20090212-2343-8336-0348/bork.txt' from the cache
And I store the file
Then the contents of the file should be 'this is a file'
Version data entries
20 entries across 20 versions & 5 rubygems