Remove skipOnStable2.0 tag (#6959)

This commit is contained in:
Swikriti Tripathi authored and GitHub committed 2023-08-03 23:06:30 +02:00
1 parent 4a4bf3ec30
commit 389877e56d
8 files changed
+36 -40

No files matched your search

@@ -43,7 +43,7 @@ Feature: edit user
| empty mail | | 400 | brian@example.com |
| change to a invalid email | invalidEmail | 400 | brian@example.com |
@skipOnStable2.0 @issue-5763
@issue-5763
Scenario Outline: 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
@@ -70,7 +70,7 @@ Feature: edit user
| change to existing user name | Brian | 409 | Brian |
| empty user name | | 400 | Brian |
@skipOnStable2.0
Scenario: 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 |
@@ -96,7 +96,7 @@ Feature: edit user
}
"""
@skipOnStable2.0
Scenario: 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 |
@@ -318,7 +318,7 @@ Feature: edit user
| User Light | User Light |
| User Light | Admin |
@skipOnStable2.0
Scenario: admin user disables another user
When the user "Alice" disables user "Brian" using the Graph API
Then the HTTP status code should be "200"
@@ -360,7 +360,7 @@ Feature: edit user
}
"""
@skipOnStable2.0
Scenario Outline: 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 assigned the role "<role>" to user "Brian" using the Graph API
@@ -409,7 +409,7 @@ Feature: edit user
| User |
| User Light |
@skipOnStable2.0
Scenario: 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
@@ -452,7 +452,7 @@ Feature: edit user
}
"""
@skipOnStable2.0
Scenario Outline: 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