From 23b3f9d7aafbc6dd543ac717d022f693443c45c1 Mon Sep 17 00:00:00 2001 From: Prajwol Amatya Date: Fri, 22 Nov 2024 13:07:49 +0545 Subject: [PATCH] update add user test for apiAccountsHashDifficulty test suite --- .../apiAccountsHashDifficulty/addUser.feature | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature b/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature index 028021397..b17225827 100644 --- a/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature +++ b/tests/acceptance/features/apiAccountsHashDifficulty/addUser.feature @@ -8,15 +8,12 @@ Feature: add user See https://github.com/owncloud/ocis/issues/1542 and https://github.com/owncloud/ocis/pull/839 - Scenario Outline: admin creates a user - 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 "" - And the HTTP status code should be "200" + Scenario: admin creates a user + When the user "Admin" creates a new user with the following attributes using the Graph API: + | userName | brand-new-user | + | displayName | Brand New User | + | email | new@example.org | + | password | %alt1% | + Then the HTTP status code should be "201" 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 | - | 1 | 100 | - | 2 | 200 | + And user "brand-new-user" should be able to upload file "filesForUpload/lorem.txt" to "lorem.txt"