Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test for chunking upload #212

Merged
merged 2 commits into from
Jun 6, 2018
Merged

Test for chunking upload #212

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5361d39
test for chunking upload #198
IljaN May 30, 2018
3cf1e8b
Add more verification steps
Jun 5, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions tests/acceptance/features/apiGuests/guests.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,40 @@ Feature: Guests
When user "[email protected]" uploads file "data/textfile.txt" to "/tmp/textfile.txt" using the API
Then the HTTP status code should be "201"

@mailhog
Scenario: A guest user can upload chunked files
Given as user "admin"
And user "user0" has been created
And user "admin" has created guest user "guest" with email "[email protected]"
And the HTTP status code should be "201"
And user "user0" has created a folder "/tmp"
And user "user0" has shared folder "/tmp" with user "[email protected]"
And guest user "guest" has registered
When user "[email protected]" creates a new chunking upload with id "chunking-42" using the API
And user "[email protected]" uploads new chunk file "1" with "AAAAA" to id "chunking-42" using the API
And user "[email protected]" uploads new chunk file "2" with "BBBBB" to id "chunking-42" using the API
And user "[email protected]" uploads new chunk file "3" with "CCCCC" to id "chunking-42" using the API
And user "[email protected]" moves new chunk file with id "chunking-42" to "/tmp/myChunkedFile.txt" using the API
Then as "[email protected]" the file "/tmp/myChunkedFile.txt" should exist
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can also add:

And as "user0" the file "/tmp/myChunkedFile.txt" should exist

just to be sure it ended up where it should.

And as "user0" the file "/tmp/myChunkedFile.txt" should exist

@mailhog
Scenario: A guest user can cancel a chunked upload
Given as user "admin"
And user "user0" has been created
And user "admin" has created guest user "guest" with email "[email protected]"
And the HTTP status code should be "201"
And user "user0" has created a folder "/tmp"
And user "user0" has shared folder "/tmp" with user "[email protected]"
And guest user "guest" has registered
When user "[email protected]" creates a new chunking upload with id "chunking-42" using the API
And user "[email protected]" uploads new chunk file "1" with "AAAAA" to id "chunking-42" using the API
And user "[email protected]" uploads new chunk file "2" with "BBBBB" to id "chunking-42" using the API
And user "[email protected]" uploads new chunk file "3" with "CCCCC" to id "chunking-42" using the API
And user "[email protected]" cancels chunking-upload with id "chunking-42" using the API
Then the HTTP status code should be "204"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you are feeling like really making sure, you can say:

And as "user0" the file "/tmp/myChunkedFile.txt" should not exist

to be sure the file did not arrive. (Make sure the HTTP status did not lie)
(it seems odd to me that the cancel of chunking is status 204 - but I guess that indicates the cancel was successful)

And as "user0" the file "/tmp/myChunkedFile.txt" should not exist

@mailhog
Scenario: A guest user can upload a file and can reshare it
Given as user "admin"
Expand Down