447 lines
13 KiB
Gherkin
447 lines
13 KiB
Gherkin
Feature: get groups and their members
|
|
As an admin
|
|
I want to be able to get groups
|
|
So that I can see all the groups and their members
|
|
|
|
Background:
|
|
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
|
|
And group "h2o-lover" has been created
|
|
When user "Alice" gets all the groups using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the extra groups returned by the API should be
|
|
| tea-lover |
|
|
| coffee-lover |
|
|
| h2o-lover |
|
|
|
|
@issue-5938
|
|
Scenario Outline: user other than the admin shouldn't get the groups list
|
|
Given user "Brian" 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
|
|
And group "tea-lover" has been created
|
|
And group "coffee-lover" has been created
|
|
And group "h2o-lover" has been created
|
|
When user "Brian" gets all the groups using the Graph API
|
|
Then the HTTP status code should be "403"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"type": "string",
|
|
"enum": ["Unauthorized"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| role |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: admin user gets users of a group
|
|
Given these users have been created with default attributes and without skeleton files:
|
|
| username |
|
|
| Brian |
|
|
| Carol |
|
|
And group "tea-lover" has been created
|
|
And user "Brian" has been added to group "tea-lover"
|
|
And user "Carol" has been added to group "tea-lover"
|
|
When user "Alice" gets all the members of group "tea-lover" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the users returned by the API should be
|
|
| Brian |
|
|
| Carol |
|
|
|
|
@issue-5938
|
|
Scenario Outline: user other than the admin shouldn't get users of a group
|
|
Given user "Brian" 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
|
|
And group "tea-lover" has been created
|
|
When user "Brian" gets all the members of group "tea-lover" using the Graph API
|
|
Then the HTTP status code should be "403"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"type": "string",
|
|
"enum": ["Unauthorized"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| role |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: admin user gets all groups along with its member's information
|
|
Given these users have been created with default attributes and without skeleton files:
|
|
| username |
|
|
| Brian |
|
|
| Carol |
|
|
And group "tea-lover" has been created
|
|
And group "coffee-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "coffee-lover"
|
|
And user "Carol" has been added to group "tea-lover"
|
|
When user "Alice" retrieves all groups along with their members using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should contain the group "coffee-lover" in the item 'value', the group-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"members"
|
|
],
|
|
"properties": {
|
|
"members": {
|
|
"type": "array",
|
|
"items": [
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should contain the group "tea-lover" in the item 'value', the group-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"members"
|
|
],
|
|
"properties": {
|
|
"members": {
|
|
"type": "array",
|
|
"items": [
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Alice"]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Carol King"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["carol@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Carol"]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
@issue-5938
|
|
Scenario Outline: user other than the admin shouldn't get all groups along with its member's information
|
|
Given user "Brian" 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
|
|
And group "tea-lover" has been created
|
|
And group "coffee-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "coffee-lover"
|
|
When user "Brian" retrieves all groups along with their members using the Graph API
|
|
Then the HTTP status code should be "403"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"type": "string",
|
|
"enum": ["Unauthorized"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| role |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: admin user gets a group along with its member's information
|
|
Given user "Brian" has been created with default attributes and without skeleton files
|
|
And group "tea-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "tea-lover"
|
|
When user "Alice" gets all the members information of group "tea-lover" using the Graph API
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"members"
|
|
],
|
|
"properties": {
|
|
"members": {
|
|
"type": "array",
|
|
"items": [
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Alice"]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
@issue-5604
|
|
Scenario Outline: user other than the admin gets a group along with its member's information
|
|
Given user "Brian" 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
|
|
And group "tea-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "tea-lover"
|
|
When user "Brian" gets all the members information of group "tea-lover" using the Graph API
|
|
Then the HTTP status code should be "403"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"type": "string",
|
|
"enum": ["Unauthorized"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| role |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: get details of a group
|
|
Given group "tea-lover" has been created
|
|
When user "Alice" gets details of the group "tea-lover" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["tea-lover"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%group_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario Outline: get details of group with UTF-8 characters name
|
|
Given group "<group>" has been created
|
|
When user "Alice" gets details of the group "<group>" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["<group>"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%group_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| group |
|
|
| España§àôœ€ |
|
|
| नेपाली |
|
|
| $x<=>[y*z^2+1]! |
|
|
| եòɴԪ˯ΗՐΛɔπ |
|
|
|
|
|
|
Scenario: admin user tries to get group information of non-existing group
|
|
When user "Alice" gets details of the group "non-existing" using the Graph API
|
|
Then the HTTP status code should be "404"
|