diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature b/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature index 4d7b03b80..f7bee673a 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature @@ -9,14 +9,14 @@ Feature: add user Scenario Outline: admin creates a user - Given using OCS API version "" + Given using OCS API version "" And user "brand-new-user" has been deleted When the administrator sends a user creation request for user "brand-new-user" password "%alt1%" using the provisioning API - Then the OCS status code should be "" + Then the OCS status code should be "" And the HTTP status code should be "200" And user "brand-new-user" should exist And user "brand-new-user" should be able to access a skeleton file Examples: - | ocs_api_version | ocs_status_code | + | ocs-api-version | ocs-status-code | | 1 | 100 | | 2 | 200 | diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature b/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature index cdcd27106..e4ec81b78 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/assignRole.feature @@ -6,11 +6,11 @@ Feature: assign role Scenario Outline: only admin user can see all existing roles Given user "Alice" has been created with default attributes and without skeleton files - And the administrator has given "Alice" the role "" using the settings api + And the administrator has given "Alice" the role "" using the settings api When user "Alice" tries to get all existing roles - Then the HTTP status code should be "" + Then the HTTP status code should be "" Examples: - | userRole | statusCode | + | user-role | http-status-code | | Admin | 201 | | Space Admin | 201 | | User | 201 | @@ -18,11 +18,11 @@ Feature: assign role @issue-5032 Scenario Outline: only admin user can see assignments list Given user "Alice" has been created with default attributes and without skeleton files - And the administrator has given "Alice" the role "" using the settings api + And the administrator has given "Alice" the role "" using the settings api When user "Alice" tries to get list of assignment - Then the HTTP status code should be "" + Then the HTTP status code should be "" Examples: - | userRole | statusCode | + | user-role | http-status-code | | Admin | 201 | | Space Admin | 401 | | User | 401 | @@ -30,12 +30,12 @@ Feature: assign role Scenario Outline: a user cannot change own role Given user "Alice" has been created with default attributes and without skeleton files - And the administrator has given "Alice" the role "" using the settings api - When user "Alice" changes his own role to "" + And the administrator has given "Alice" the role "" using the settings api + When user "Alice" changes his own role to "" Then the HTTP status code should be "400" - And user "Alice" should have the role "" + And user "Alice" should have the role "" Examples: - | userRole | desiredRole | + | user-role | desired-role | | Admin | User | | Admin | Space Admin | | Space Admin | Admin | @@ -49,12 +49,12 @@ Feature: assign role | username | | Alice | | Brian | - And the administrator has given "Alice" the role "" using the settings api - When user "Alice" changes the role "" for user "Brian" - Then the HTTP status code should be "" - And user "Brian" should have the role "" + And the administrator has given "Alice" the role "" using the settings api + When user "Alice" changes the role "" for user "Brian" + Then the HTTP status code should be "" + And user "Brian" should have the role "" Examples: - | userRole | desiredRole | statusCode | expectedRole | + | user-role | desired-role | http-status-code | expected-role | | Admin | User | 201 | User | | Admin | Space Admin | 201 | Space Admin | | Admin | Admin | 201 | Admin | diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature b/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature index 2f606e964..df198e482 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature @@ -9,13 +9,13 @@ Feature: sharing Scenario Outline: creating a share of a file with a user - Given using OCS API version "" + Given using OCS API version "" And user "Alice" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt" And user "Brian" has been created with default attributes and without skeleton files When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0" Examples: - | ocs_api_version | + | ocs-api-version | | 1 | - | 2 | \ No newline at end of file + | 2 | diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature b/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature index df9a0aa3f..04232a2be 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/uploadFile.feature @@ -9,13 +9,13 @@ Feature: upload file Scenario Outline: upload a file and check download content - Given using OCS API version "" + Given using OCS API version "" And user "Alice" has been created with default attributes and without skeleton files And using DAV path When user "Alice" uploads file with content "uploaded content" to "/upload.txt" using the WebDAV API Then the content of file "/upload.txt" for user "Alice" should be "uploaded content" Examples: - | ocs_api_version | dav-path-version | + | ocs-api-version | dav-path-version | | 1 | old | | 1 | new | | 2 | old |