Modified test to PUT only 1 parameter with each update

This commit is contained in:
Sergio Bertolin 2015-11-12 10:36:17 +00:00
parent eb6a13c231
commit ce8435530b
1 changed files with 86 additions and 4 deletions

View File

@ -72,14 +72,13 @@ Feature: sharing
| path | welcome.txt |
| shareType | 3 |
| password | publicpw |
#And Adding expiration date to last share
And Updating last share with
| expireDate | +3 days |
Then the OCS status code should be "100"
And the HTTP status code should be "200"
And Public shared file "welcome.txt" with password "publicpw" can be downloaded
Scenario: Creating a new public share, updating it and getting it's info
Scenario: Creating a new public share, updating its expiration date and getting its info
Given user "user0" exists
And As an "user0"
When creating a public share with
@ -87,8 +86,64 @@ Feature: sharing
| shareType | 3 |
And Updating last share with
| expireDate | +3 days |
And Getting info of last share
Then the OCS status code should be "100"
And the HTTP status code should be "200"
And Share fields of last share match with
| id | A_NUMBER |
| item_type | folder |
| item_source | A_NUMBER |
| share_type | 3 |
| file_source | A_NUMBER |
| file_target | /FOLDER |
| permissions | 1 |
| stime | A_NUMBER |
| expiration | +3 days |
| token | A_TOKEN |
| storage | A_NUMBER |
| mail_send | 0 |
| uid_owner | user0 |
| storage_id | home::user0 |
| file_parent | A_NUMBER |
| displayname_owner | user0 |
| url | AN_URL |
Scenario: Creating a new public share, updating its password and getting its info
Given user "user0" exists
And As an "user0"
When creating a public share with
| path | FOLDER |
| shareType | 3 |
And Updating last share with
| password | publicpw |
| publicUpload | true |
And Getting info of last share
Then the OCS status code should be "100"
And the HTTP status code should be "200"
And Share fields of last share match with
| id | A_NUMBER |
| item_type | folder |
| item_source | A_NUMBER |
| share_type | 3 |
| file_source | A_NUMBER |
| file_target | /FOLDER |
| permissions | 1 |
| stime | A_NUMBER |
| token | A_TOKEN |
| storage | A_NUMBER |
| mail_send | 0 |
| uid_owner | user0 |
| storage_id | home::user0 |
| file_parent | A_NUMBER |
| displayname_owner | user0 |
| url | AN_URL |
Scenario: Creating a new public share, updating its permissions and getting its info
Given user "user0" exists
And As an "user0"
When creating a public share with
| path | FOLDER |
| shareType | 3 |
And Updating last share with
| permissions | 7 |
And Getting info of last share
Then the OCS status code should be "100"
@ -102,7 +157,6 @@ Feature: sharing
| file_target | /FOLDER |
| permissions | 7 |
| stime | A_NUMBER |
| expiration | +3 days |
| token | A_TOKEN |
| storage | A_NUMBER |
| mail_send | 0 |
@ -112,6 +166,34 @@ Feature: sharing
| displayname_owner | user0 |
| url | AN_URL |
Scenario: Creating a new public share, updating publicUpload option and getting its info
Given user "user0" exists
And As an "user0"
When creating a public share with
| path | FOLDER |
| shareType | 3 |
And Updating last share with
| publicUpload | true |
And Getting info of last share
Then the OCS status code should be "100"
And the HTTP status code should be "200"
And Share fields of last share match with
| id | A_NUMBER |
| item_type | folder |
| item_source | A_NUMBER |
| share_type | 3 |
| file_source | A_NUMBER |
| file_target | /FOLDER |
| permissions | 7 |
| stime | A_NUMBER |
| token | A_TOKEN |
| storage | A_NUMBER |
| mail_send | 0 |
| uid_owner | user0 |
| storage_id | home::user0 |
| file_parent | A_NUMBER |
| displayname_owner | user0 |
| url | AN_URL |
Scenario: getting all shares of a user using that user
Given user "user0" exists