You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tests/acceptance/features/apiProvisioning-v1/createSubAdmin.feature
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,15 @@ Feature: create a subadmin
25
25
And the HTTP status code should be "200"
26
26
And user "nonexistentuser" should not be a subadmin of group "brand-new-group"
27
27
28
+
@smokeTest
29
+
Scenario: admin tries to create a subadmin when the subadmin feature is disabled
30
+
Given user "brand-new-user" has been created with default attributes and without skeleton files
31
+
And group "brand-new-group" has been created
32
+
When the administrator tries to make user "brand-new-user" a subadmin of group "brand-new-group" using the provisioning API with the subadmin feature disabled
33
+
Then the OCS status code should be "103"
34
+
And the HTTP status code should be "200"
35
+
And user "brand-new-user" should not be a subadmin of group "brand-new-group"
36
+
28
37
29
38
Scenario: admin tries to create a subadmin using a group which does not exist
30
39
Given user "brand-new-user" has been created with default attributes and without skeleton files
0 commit comments