Skip to content

Commit

Permalink
test: Test coverage for bug #10051
Browse files Browse the repository at this point in the history
  • Loading branch information
anon-pradip committed Oct 1, 2024
1 parent 0fb5021 commit 28b8ee4
Showing 1 changed file with 55 additions and 0 deletions.
55 changes: 55 additions & 0 deletions tests/acceptance/features/apiOcm/share.feature
Original file line number Diff line number Diff line change
Expand Up @@ -171,3 +171,58 @@ Feature: an user shares resources usin ScienceMesh application
}
}
"""


Scenario Outline: user tries to add federated user to a space
Given using server "LOCAL"
And "Alice" has created the federation share invitation
And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
And using spaces DAV path
And user "Alice" has created a space "NewSpace" with the default quota using the Graph API
And using server "REMOTE"
And "Brian" has accepted invitation
And using server "LOCAL"
When user "Alice" sends the following space share invitation to federated user using the Graph API:
| space | NewSpace |
| sharee | Brian |
| shareType | user |
| permissionsRole | <permissions-role> |
| federatedServer | @ocis-server:9200 |
Then the HTTP status code should be "400"
And the JSON data of the response should match
"""
{
"type": "object",
"required": ["error"],
"properties": {
"error": {
"type": "object",
"required": [
"code",
"innererror",
"message"
],
"properties": {
"code" : {
"const": "invalidRequest"
},
"innererror" : {
"type": "object",
"required": [
"date",
"request-id"
]
},
"message" : {
"const": "federated user can not become a space member"
}
}
}
}
}
"""
Examples:
| permissions-role |
| Space Viewer |
| Space Editor |
| Manager |

0 comments on commit 28b8ee4

Please sign in to comment.