sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reformat gherkin tables

Browse Source
This commit is contained in:
Phil Davis
2020-10-16 13:30:54 +05:45
parent 3014e53ee1
commit 314eff4e94
8 changed files with 69 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsDELETEAuth.feature
+12 -12
View File
@@ -22,37 +22,37 @@ Feature: auth
Scenario: send DELETE requests to OCS endpoints as admin with wrong password Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice" When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users/%username% | | /ocs/v1.php/cloud/users/%username% |
| /ocs/v1.php/cloud/users/%username%/subadmins | | /ocs/v1.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice" When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username% | | /ocs/v2.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "404" Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice" When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users/%username%/groups | | /ocs/v1.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "996" And the OCS status code of responses on all endpoints should be "996"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice" When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username%/groups | | /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "500" Then the HTTP status code of responses on all endpoints should be "500"
And the OCS status code of responses on all endpoints should be "996" And the OCS status code of responses on all endpoints should be "996"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice" When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username% | | /ocs/v2.php/cloud/users/%username% |
| /ocs/v2.php/cloud/users/%username%/subadmins | | /ocs/v2.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "404" Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsPOSTAuth.feature
+12 -12
View File
@@ -31,13 +31,13 @@ Feature: auth
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send POST requests to OCS endpoints as normal user with wrong password Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice" When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users | | /ocs/v1.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "400" And the OCS status code of responses on all endpoints should be "400"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice" When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users | | /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "400" Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "400" And the OCS status code of responses on all endpoints should be "400"
@@ -45,13 +45,13 @@ Feature: auth
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send POST requests to OCS endpoints as normal user with wrong password Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice" When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users/%username%/groups | | /ocs/v1.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "400" And the OCS status code of responses on all endpoints should be "400"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice" When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username%/groups | | /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "400" Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "400" And the OCS status code of responses on all endpoints should be "400"
@@ -59,12 +59,12 @@ Feature: auth
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send POST requests to OCS endpoints as normal user with wrong password Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice" When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users/%username%/subadmins | | /ocs/v1.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice" When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username%/subadmins | | /ocs/v2.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "404" Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsPUTAuth.feature
+10 -10
View File
@@ -17,13 +17,13 @@ Feature: auth
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send PUT request to OCS endpoints as admin with wrong password Scenario: send PUT request to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice" When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users/%username% | | /ocs/v1.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "103" And the OCS status code of responses on all endpoints should be "103"
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice" When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username% | | /ocs/v2.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "400" Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "103" And the OCS status code of responses on all endpoints should be "103"
@@ -32,15 +32,15 @@ Feature: auth
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send PUT request to OCS endpoints as admin with wrong password Scenario: send PUT request to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice" When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v1.php/cloud/users/%username%/disable | | /ocs/v1.php/cloud/users/%username%/disable |
| /ocs/v1.php/cloud/users/%username%/enable | | /ocs/v1.php/cloud/users/%username%/enable |
Then the HTTP status code of responses on all endpoints should be "200" Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice" When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint | | endpoint |
| /ocs/v2.php/cloud/users/%username%/disable | | /ocs/v2.php/cloud/users/%username%/disable |
| /ocs/v2.php/cloud/users/%username%/enable | | /ocs/v2.php/cloud/users/%username%/enable |
Then the HTTP status code of responses on all endpoints should be "404" Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998" And the OCS status code of responses on all endpoints should be "998"
ocis/tests/acceptance/features/apiOcisSpecific/apiShareCreateSpecial2-createShareWithInvalidPermissions.feature
+7 -7
View File
@@ -21,8 +21,8 @@ Feature: cannot share resources with invalid permissions
And as "Brian" entry "textfile0.txt" should not exist And as "Brian" entry "textfile0.txt" should not exist
Examples: Examples:
| ocs_api_version | ocs_status_code | eos_status_code | http_status_code_ocs | http_status_code_eos | | ocs_api_version | ocs_status_code | eos_status_code | http_status_code_ocs | http_status_code_eos |
| 1 | 100 | 996 | 200 | 500 | | 1 | 100 | 996 | 200 | 500 |
| 2 | 200 | 996 | 200 | 500 | | 2 | 200 | 996 | 200 | 500 |
@issue-ocis-reva-45 @issue-ocis-reva-243 @issue-ocis-reva-45 @issue-ocis-reva-243
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
@@ -38,8 +38,8 @@ Feature: cannot share resources with invalid permissions
And the HTTP status code should be "<http_status_code_ocs>" or "<http_status_code_eos>" And the HTTP status code should be "<http_status_code_ocs>" or "<http_status_code_eos>"
And as "Brian" entry "textfile0.txt" should not exist And as "Brian" entry "textfile0.txt" should not exist
Examples: Examples:
| ocs_api_version | eos_status_code | ocs_status_code | http_status_code_ocs | http_status_code_eos | permissions | | ocs_api_version | eos_status_code | ocs_status_code | http_status_code_ocs | http_status_code_eos | permissions |
| 1 | 100 | 996 | 200 | 500 | delete | | 1 | 100 | 996 | 200 | 500 | delete |
| 2 | 200 | 996 | 200 | 500 | delete | | 2 | 200 | 996 | 200 | 500 | delete |
| 1 | 100 | 996 | 200 | 500 | create,delete | | 1 | 100 | 996 | 200 | 500 | create,delete |
| 2 | 200 | 996 | 200 | 500 | create,delete | | 2 | 200 | 996 | 200 | 500 | create,delete |
ocis/tests/acceptance/features/apiOcisSpecific/apiShareManagementBasic-createShare.feature
+12 -12
View File
@@ -53,8 +53,8 @@ Feature: sharing
And as "Brian" file "randomfile.txt" should not exist And as "Brian" file "randomfile.txt" should not exist
Examples: Examples:
| ocs_api_version | http_status_code_ocs | http_status_code_eos | | ocs_api_version | http_status_code_ocs | http_status_code_eos |
| 1 | 200 | 500 | | 1 | 200 | 500 |
| 2 | 200 | 500 | | 2 | 200 | 500 |
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-301 @issue-ocis-reva-302 @skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-301 @issue-ocis-reva-302
# after fixing all issues delete this Scenario and use the one from oC10 core # after fixing all issues delete this Scenario and use the one from oC10 core
@@ -66,16 +66,16 @@ Feature: sharing
Then the OCS status code should be "<ocs_status_code>" Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200" And the HTTP status code should be "200"
And the fields of the last response to user "Alice" sharing with user "Brian" should include And the fields of the last response to user "Alice" sharing with user "Brian" should include
| share_with | %username% | | share_with | %username% |
| file_target | /FOLDER | | file_target | /FOLDER |
| path | /FOLDER | | path | /FOLDER |
| permissions | all | | permissions | all |
| uid_owner | %username% | | uid_owner | %username% |
| displayname_owner | | | displayname_owner | |
| item_type | folder | | item_type | folder |
| mimetype | httpd/unix-directory | | mimetype | httpd/unix-directory |
| storage_id | ANY_VALUE | | storage_id | ANY_VALUE |
| share_type | user | | share_type | user |
And the fields of the last response should not include And the fields of the last response should not include
| share_with_displayname | %displayname% | | share_with_displayname | %displayname% |
Examples: Examples:
ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink1-createPublicLinkShare.feature
+1 -1
View File
@@ -23,7 +23,7 @@ Feature: create a public link share
Given user "Alice" has created folder "testFolder" Given user "Alice" has created folder "testFolder"
When user "Alice" uploads file with content "uploaded content for file name ending with a dot" to "testFolder/file.txt" using the WebDAV API When user "Alice" uploads file with content "uploaded content for file name ending with a dot" to "testFolder/file.txt" using the WebDAV API
And user "Alice" has created a public link share with settings And user "Alice" has created a public link share with settings
| path | /testFolder | | path | /testFolder |
| permissions | read,update,create,delete | | permissions | read,update,create,delete |
And the public uploads file "file.txt" to the last shared folder with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the new public WebDAV API And the public uploads file "file.txt" to the last shared folder with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the new public WebDAV API
Then as "Alice" file "/testFolder/file.txt" should exist Then as "Alice" file "/testFolder/file.txt" should exist
ocis/tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature
+12 -12
View File
@@ -59,18 +59,18 @@ Feature: sharing
When user "Brian" moves folder "/Alice-folder/folder2" to "/Carol-folder/folder2" using the WebDAV API When user "Brian" moves folder "/Alice-folder/folder2" to "/Carol-folder/folder2" using the WebDAV API
And user "Carol" gets the info of the last share using the sharing API And user "Carol" gets the info of the last share using the sharing API
Then the fields of the last response to user "Carol" sharing with user "Brian" should include Then the fields of the last response to user "Carol" sharing with user "Brian" should include
| id | A_STRING | | id | A_STRING |
| item_type | folder | | item_type | folder |
| item_source | A_STRING | | item_source | A_STRING |
| share_type | user | | share_type | user |
| file_source | A_STRING | | file_source | A_STRING |
| file_target | /Carol-folder | | file_target | /Carol-folder |
| permissions | all | | permissions | all |
| stime | A_NUMBER | | stime | A_NUMBER |
| storage | A_STRING | | storage | A_STRING |
| mail_send | 0 | | mail_send | 0 |
| uid_owner | %username% | | uid_owner | %username% |
| mimetype | httpd/unix-directory | | mimetype | httpd/unix-directory |
And as "Alice" folder "/Alice-folder/folder2" should exist And as "Alice" folder "/Alice-folder/folder2" should exist
And as "Carol" folder "/Carol-folder/folder2" should not exist And as "Carol" folder "/Carol-folder/folder2" should not exist
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature
+3 -3
View File
@@ -15,9 +15,9 @@ Feature: upload file
When user "Alice" uploads file with content "uploaded content" to <file_name> using the WebDAV API When user "Alice" uploads file with content "uploaded content" to <file_name> using the WebDAV API
Then the content of file <file_name> for user "Alice" should be "" Then the content of file <file_name> for user "Alice" should be ""
Examples: Examples:
| dav_version | file_name | | dav_version | file_name |
| old | "file ?2.txt" | | old | "file ?2.txt" |
| new | "file ?2.txt" | | new | "file ?2.txt" |
@skipOnOcis-OC-Storage @issue-product-127 @skipOnOcis-OCIS-Storage @skipOnOcis-OC-Storage @issue-product-127 @skipOnOcis-OCIS-Storage
# this scenario passes/fails intermittently on OC storage, so do not run it in CI # this scenario passes/fails intermittently on OC storage, so do not run it in CI