forked from carrierwaveuploader/carrierwave
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathversions_overridden_filename.feature
51 lines (46 loc) · 3.26 KB
/
versions_overridden_filename.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Feature: uploader with file storage and overriden filename
In order to customize the filaname of uploaded files
As a developer using CarrierWave
I want to upload files to the filesystem with an overriden filename and different verions
Background:
Given an uploader class that uses the 'file' storage
And that the uploader class has a version named 'thumb'
And that the uploader has the filename overridden to 'grark.png'
And an instance of that class
Scenario: store a file
When I store the file 'fixtures/bork.txt'
Then there should be a file at 'public/uploads/grark.png'
Then there should be a file at 'public/uploads/thumb_grark.png'
And the file at 'public/uploads/grark.png' should be identical to the file at 'fixtures/bork.txt'
And the file at 'public/uploads/thumb_grark.png' should be identical to the file at 'fixtures/bork.txt'
And the uploader should have the url '/uploads/grark.png'
And the uploader's version 'thumb' should have the url '/uploads/thumb_grark.png'
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'
Then there should be a file called 'thumb_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/grark.png'
And there should not be a file at 'public/uploads/thumb_grark.png'
When I store the file
Then there should be a file at 'public/uploads/grark.png'
And there should be a file at 'public/uploads/thumb_grark.png'
And the file at 'public/uploads/grark.png' should be identical to the file at 'fixtures/bork.txt'
And the file at 'public/uploads/thumb_grark.png' should be identical to the file at 'fixtures/bork.txt'
And the uploader should have the url '/uploads/grark.png'
And the uploader's version 'thumb' should have the url '/uploads/thumb_grark.png'
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'
Given the file 'fixtures/monkey.txt' is cached file at 'public/uploads/tmp/20090212-2343-8336-0348/thumb_bork.txt'
When I retrieve the cache name '20090212-2343-8336-0348/bork.txt' from the cache
And I store the file
Then there should be a file at 'public/uploads/grark.png'
Then there should be a file at 'public/uploads/thumb_grark.png'
And the file at 'public/uploads/grark.png' should be identical to the file at 'fixtures/bork.txt'
And the file at 'public/uploads/thumb_grark.png' should be identical to the file at 'fixtures/monkey.txt'
Scenario: retrieving a file from store
Given the file 'fixtures/bork.txt' is stored at 'public/uploads/bork.txt'
Given the file 'fixtures/monkey.txt' is stored at 'public/uploads/thumb_bork.txt'
When I retrieve the file 'bork.txt' from the store
Then the uploader should have the url '/uploads/bork.txt'
And the uploader's version 'thumb' should have the url '/uploads/thumb_bork.txt'