removing @api tag from all acceptance feature files (#7027)
This commit is contained in:
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: add users to group
|
||||
As a admin
|
||||
I want to be able to add users to a group
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: assign role
|
||||
As an admin,
|
||||
I want to assign roles to users.
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: an user changes its own password
|
||||
As a user
|
||||
I want to change my password
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: change role
|
||||
As an admin
|
||||
I want to change the role of user
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: create group
|
||||
As an admin
|
||||
I want to create a group
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: create groups, group names are case insensitive
|
||||
As an admin
|
||||
I want to create groups with similar cases
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: create user
|
||||
As a admin
|
||||
I want to create a user
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: delete groups
|
||||
As an admin
|
||||
I want to be able to delete groups
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: delete user
|
||||
As an admin
|
||||
I want to be able to delete users
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: edit group name
|
||||
As an admin
|
||||
I want to be able to edit group name
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: edit user
|
||||
As an admin
|
||||
I want to be able to edit user information
|
||||
@@ -70,7 +69,7 @@ Feature: edit user
|
||||
| change to existing user name | Brian | 409 | Brian |
|
||||
| empty user name | | 400 | Brian |
|
||||
|
||||
|
||||
|
||||
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 +95,7 @@ Feature: edit user
|
||||
}
|
||||
"""
|
||||
|
||||
|
||||
|
||||
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 +317,7 @@ Feature: edit user
|
||||
| User Light | User Light |
|
||||
| User Light | Admin |
|
||||
|
||||
|
||||
|
||||
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 +359,7 @@ Feature: edit user
|
||||
}
|
||||
"""
|
||||
|
||||
|
||||
|
||||
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 +408,7 @@ Feature: edit user
|
||||
| User |
|
||||
| User Light |
|
||||
|
||||
|
||||
|
||||
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 +451,7 @@ Feature: edit user
|
||||
}
|
||||
"""
|
||||
|
||||
|
||||
|
||||
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
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
@api @env-config
|
||||
@env-config
|
||||
Feature: enforce password on public link
|
||||
As a user
|
||||
I want to enforce passwords on public links shared with upload, edit, or contribute permission
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: full text search
|
||||
As a user
|
||||
I want to do full text search
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: get applications
|
||||
As a user
|
||||
I want to be able to get application information with existing roles
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: get groups and their members
|
||||
As an admin
|
||||
I want to be able to get groups
|
||||
@@ -8,7 +7,7 @@ Feature: get groups and their members
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
|
||||
|
||||
|
||||
Scenario: admin user lists all the groups
|
||||
Given group "tea-lover" has been created
|
||||
And group "coffee-lover" has been created
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: get users
|
||||
As an admin
|
||||
I want to be able to retrieve user information
|
||||
@@ -10,7 +9,7 @@ Feature: get users
|
||||
| Alice |
|
||||
| Brian |
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets the information of a user
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
When user "Alice" gets information of user "Brian" using Graph API
|
||||
@@ -93,7 +92,7 @@ Feature: get users
|
||||
| User Light | User Light |
|
||||
| User Light | Admin |
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets all users
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
When user "Alice" gets all users using the Graph API
|
||||
@@ -159,7 +158,7 @@ Feature: get users
|
||||
}
|
||||
"""
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets all users include disabled users
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
And the user "Alice" has disabled user "Brian" using the Graph API
|
||||
@@ -258,7 +257,7 @@ Feature: get users
|
||||
| User |
|
||||
| User Light |
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets the drive information of a user
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
When the user "Alice" gets user "Brian" along with his drive information using Graph API
|
||||
@@ -381,7 +380,7 @@ Feature: get users
|
||||
}
|
||||
"""
|
||||
|
||||
|
||||
|
||||
Scenario Outline: non-admin user gets his/her own drive information
|
||||
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
|
||||
When the user "Brian" gets his drive information using Graph API
|
||||
@@ -509,7 +508,7 @@ Feature: get users
|
||||
| User |
|
||||
| User Light |
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets the group information of a user
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
And group "tea-lover" has been created
|
||||
@@ -617,7 +616,7 @@ Feature: get users
|
||||
| User Light | User Light |
|
||||
| User Light | Admin |
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets all users of certain groups
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
@@ -751,7 +750,7 @@ Feature: get users
|
||||
And the JSON data of the response should not contain the user "Alice Hansen" in the item 'value'
|
||||
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets all users of two groups
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
@@ -825,7 +824,7 @@ Feature: get users
|
||||
"""
|
||||
But the JSON data of the response should not contain the user "Carol King" in the item 'value'
|
||||
|
||||
|
||||
|
||||
Scenario Outline: non admin user tries to get users of certain groups
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
|
||||
@@ -860,7 +859,7 @@ Feature: get users
|
||||
| User |
|
||||
| User Light |
|
||||
|
||||
|
||||
|
||||
Scenario: admin user gets all users with certain roles and members of a certain group
|
||||
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
||||
And user "Carol" has been created with default attributes and without skeleton files
|
||||
@@ -965,7 +964,7 @@ Feature: get users
|
||||
"""
|
||||
But the JSON data of the response should not contain the user "Carol King" in the item 'value'
|
||||
|
||||
|
||||
|
||||
Scenario Outline: non-admin user tries to get users with a certain role
|
||||
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
|
||||
When the user "Alice" gets all users with role "<role>" using the Graph API
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: get user's own information
|
||||
As user
|
||||
I want to be able to retrieve my own information
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: remove a user from a group
|
||||
As an admin
|
||||
I want to be able to remove a user from a group
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: unassign user role
|
||||
As an admin
|
||||
I want to unassign the role of user
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
@api
|
||||
Feature: user GDPR (General Data Protection Regulation) report
|
||||
As a user
|
||||
I want to generate my GDPR report
|
||||
|
||||
Reference in New Issue
Block a user