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

add skip on stable tag (#5940)

Browse Source
This commit is contained in:
Swikriti Tripathi
2023-03-28 15:11:41 +05:45
committed by GitHub
parent 382aa58c8b
commit 270bf06840
11 changed files with 66 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiGraph/assignRole.feature
+1 -1
View File
@@ -1,4 +1,4 @@
@api
@api @skipOnStable2.0
Feature: assign role
As an admin,
I want to assign roles to users.
tests/acceptance/features/apiGraph/changeOwnPassword.feature
+14 -14
View File
@@ -2,17 +2,17 @@
Feature: an user changes its own password
Scenario Outline: change own password
Given user "Alice" has been created with default attributes and without skeleton files
When the user "Alice" changes its own password "<currentPassword>" to "<newPassword>" using the Graph API
Then the HTTP status code should be "<code>"
Examples:
| currentPassword | newPassword | code |
| 123456 | validPass | 204 |
| 123456 | кириллица | 204 |
| 123456 | 密码 | 204 |
| 123456 | ?&^%0 | 204 |
| 123456 | | 400 |
| 123456 | 123456 | 400 |
| wrongPass | 123456 | 400 |
| | validPass | 400 |
Scenario Outline: change own password
Given user "Alice" has been created with default attributes and without skeleton files
When the user "Alice" changes its own password "<currentPassword>" to "<newPassword>" using the Graph API
Then the HTTP status code should be "<code>"
Examples:
| currentPassword | newPassword | code |
| 123456 | validPass | 204 |
| 123456 | кириллица | 204 |
| 123456 | 密码 | 204 |
| 123456 | ?&^%0 | 204 |
| 123456 | | 400 |
| 123456 | 123456 | 400 |
| wrongPass | 123456 | 400 |
| | validPass | 400 |
tests/acceptance/features/apiGraph/createUser.feature
+8 -4
View File
@@ -25,11 +25,15 @@ Feature: create user
| withoutPassSameEmail | without pass | alice@example.org | | 200 | true | should |
| name | pass with space | example@example.org | my pass | 200 | true | should |
| nameWithCharacters(*:!;_+-&) | user | new@example.org | 123 | 400 | true | should not |
| withoutEmail | without email | | 123 | 200 | true | should |
| Alice | same userName | new@example.org | 123 | 400 | true | should |
| name with space | name with space | example@example.org | 123 | 400 | true | should not |
| createDisabledUser | disabled user | example@example.org | 123 | 200 | false | should |
@skipOnStable2.0
Examples:
| userName | displayName | email | password | code | enable | shouldOrNot |
| withoutEmail | without email | | 123 | 200 | true | should |
| Alice | same userName | new@example.org | 123 | 400 | true | should |
Scenario: a user cannot be created with empty name
Given the administrator has given "Alice" the role "Admin" using the settings api
@@ -58,7 +62,7 @@ Feature: create user
| User |
| Guest |
@issue-3516
@issue-3516 @skipOnStable2.0
Scenario: a user cannot be created with the name of the disabled user
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
@@ -71,7 +75,7 @@ Feature: create user
| accountEnabled | true |
Then the HTTP status code should be "400"
@skipOnStable2.0
Scenario: a user can be created with the name of the deleted user
Given user "Brian" has been created with default attributes and without skeleton files
And the administrator has given "Alice" the role "Admin" using the settings api
tests/acceptance/features/apiGraph/editUser.feature
+7 -7
View File
@@ -28,7 +28,7 @@ Feature: edit user
| empty mail | | 400 | brian@example.com |
| change to a invalid email | invalidEmail | 400 | brian@example.com |
@skipOnStable2.0
Scenario Outline: the admin user can edit another user's name
Given user "Carol" has been created with default attributes and without skeleton files
When the user "Alice" changes the user name of user "Carol" to "<userName>" using the Graph API
@@ -43,7 +43,7 @@ Feature: edit user
| change to existing user name | Brian | 409 | Brian |
| empty user name | | 400 | Brian |
@skipOnStable2.0
Scenario: the admin user changes the name of a user to the name of an existing disabled user
Given the user "Alice" has created a new user using the Graph API with the following settings:
| userName | sam |
@@ -57,7 +57,7 @@ Feature: edit user
| key | value |
| onPremisesSamAccountName | sam |
@skipOnStable2.0
Scenario: the admin user changes the name of a user to the name of a previously deleted user
Given the user "Alice" has created a new user using the Graph API with the following settings:
| userName | sam |
@@ -207,7 +207,7 @@ Feature: edit user
| Guest | Guest |
| Guest | Admin |
@skipOnStable2.0
Scenario: the admin user disables another user
When the user "Alice" disables user "Brian" using the Graph API
Then the HTTP status code should be "200"
@@ -217,7 +217,7 @@ Feature: edit user
| displayName | id | mail | onPremisesSamAccountName | accountEnabled |
| Brian Murphy | %uuid_v4% | brian@example.com | Brian | false |
@skipOnStable2.0
Scenario Outline: a normal user should not be able to disable another user
Given user "Carol" has been created with default attributes and without skeleton files
And the administrator has given "Brian" the role "<role>" using the settings api
@@ -234,7 +234,7 @@ Feature: edit user
| User |
| Guest |
@skipOnStable2.0
Scenario: the admin user enables disabled user
Given the user "Alice" has disabled user "Brian" using the Graph API
When the user "Alice" enables user "Brian" using the Graph API
@@ -245,7 +245,7 @@ Feature: edit user
| displayName | id | mail | onPremisesSamAccountName | accountEnabled |
| Brian Murphy | %uuid_v4% | brian@example.com | Brian | true |
@skipOnStable2.0
Scenario Outline: a normal user should not be able to enable another user
Given user "Carol" has been created with default attributes and without skeleton files
And the user "Alice" has disabled user "Carol" using the Graph API
tests/acceptance/features/apiGraph/getApplications.feature
+2 -2
View File
@@ -1,4 +1,4 @@
@api @skipOnOcV10
@api @skipOnOcV10 @skipOnStable2.0
Feature: get applications
As an user
I want to be able to get applications information with existings roles
@@ -25,4 +25,4 @@ Feature: get applications
| Admin |
| Space Admin |
| User |
| Guest |
| Guest |
tests/acceptance/features/apiGraph/getUser.feature
+10 -9
View File
@@ -10,7 +10,7 @@ Feature: get users
| Alice |
| Brian |
@skipOnStable2.0
Scenario: admin user gets the information of a user
Given the administrator has given "Alice" the role "Admin" using the settings api
When user "Alice" gets information of user "Brian" using Graph API
@@ -41,7 +41,7 @@ Feature: get users
| Guest | Guest |
| Guest | Admin |
@skipOnStable2.0
Scenario: admin user gets all users
Given the administrator has given "Alice" the role "Admin" using the settings api
When user "Alice" gets all users using the Graph API
@@ -51,7 +51,7 @@ Feature: get users
| Alice Hansen | %uuid_v4% | alice@example.org | Alice | true |
| Brian Murphy | %uuid_v4% | brian@example.org | Brian | true |
@skipOnStable2.0
Scenario: admin user gets all users include disabled users
Given the administrator has given "Alice" the role "Admin" using the settings api
And the user "Alice" has disabled user "Brian" using the Graph API
@@ -74,7 +74,7 @@ Feature: get users
| User |
| Guest |
@skipOnStable2.0
Scenario: admin user gets the drive information of a user
Given the administrator has given "Alice" the role "Admin" using the settings api
When the user "Alice" gets user "Brian" along with his drive information using Graph API
@@ -93,7 +93,7 @@ Feature: get users
| root@@@webDavUrl | %base_url%/dav/spaces/%space_id% |
| webUrl | %base_url%/f/%space_id% |
@skipOnStable2.0
Scenario Outline: non-admin user gets his/her own drive information
Given the administrator has given "Brian" the role "<userRole>" using the settings api
When the user "Brian" gets his drive information using Graph API
@@ -117,6 +117,7 @@ Feature: get users
| User |
| Guest |
@skipOnStable2.0
Scenario: admin user gets the group information of a user
Given the administrator has given "Alice" the role "Admin" using the settings api
And group "tea-lover" has been created
@@ -153,7 +154,7 @@ Feature: get users
| Guest | Guest |
| Guest | Admin |
@skipOnStable2.0
Scenario: admin user gets all users of certain groups
Given the administrator has given "Alice" the role "Admin" using the settings api
And user "Carol" has been created with default attributes and without skeleton files
@@ -202,7 +203,7 @@ Feature: get users
| displayName | id | mail | onPremisesSamAccountName | accountEnabled |
| Carol King | %uuid_v4% | carol@example.org | Carol | false |
@skipOnStable2.0
Scenario Outline: non admin user tries to get users of certain groups
Given the administrator has given "Alice" the role "Admin" using the settings api
And the administrator has given "Brian" the role "<role>" using the settings api
@@ -217,7 +218,7 @@ Feature: get users
| User |
| Guest |
@skipOnStable2.0
Scenario: admin user gets all users with certain roles and members of a certain group
Given the administrator has given "Alice" the role "Admin" using the settings api
And user "Carol" has been created with default attributes and without skeleton files
@@ -243,7 +244,7 @@ Feature: get users
| displayName | id | mail | onPremisesSamAccountName | accountEnabled |
| Carol King | %uuid_v4% | carol@example.org | Carol | true |
@skipOnStable2.0
Scenario Outline: non-admin user tries to get users with a certain role
Given the administrator has given "Alice" the role "<userRole>" using the settings api
When the user "Alice" gets all users with role "<role>" using the Graph API