-
Notifications
You must be signed in to change notification settings - Fork 189
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2c03dd0
commit 6d5a021
Showing
5 changed files
with
425 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
137 changes: 137 additions & 0 deletions
137
tests/acceptance/features/apiOcm/deleteFederatedConnections.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,137 @@ | ||
@ocm | ||
Feature: delete federated connections | ||
As a user | ||
I want to delete federated connections if they are no longer needed | ||
|
||
Background: | ||
Given user "Alice" has been created with default attributes and without skeleton files | ||
And using server "REMOTE" | ||
And user "Brian" has been created with default attributes and without skeleton files | ||
|
||
|
||
Scenario: users deletes federated connection | ||
Given using server "LOCAL" | ||
And "Alice" has created the federation share invitation | ||
And using server "REMOTE" | ||
And "Brian" has accepted invitation | ||
When user "Brian" deletes federated connection with user "Alice" using the Graph API | ||
Then the HTTP status code should be "200" | ||
When user "Brian" searches for federated user "alice" using Graph API | ||
Then the HTTP status code should be "200" | ||
And the JSON data of the response should match | ||
""" | ||
{ | ||
"type": "object", | ||
"required": [ | ||
"value" | ||
], | ||
"properties": { | ||
"value": { | ||
"type": "array", | ||
"minItems": 0, | ||
"maxItems": 0 | ||
} | ||
} | ||
} | ||
""" | ||
|
||
@issue-10216 | ||
Scenario: user cannot find the federated user if the user has deleted the connection | ||
Given using server "LOCAL" | ||
And "Alice" has created the federation share invitation | ||
And using server "REMOTE" | ||
And "Brian" has accepted invitation | ||
And user "Brian" has deleted federated connection with user "Alice" | ||
And using server "LOCAL" | ||
When user "Alice" searches for federated user "brian" using Graph API | ||
Then the HTTP status code should be "200" | ||
And the JSON data of the response should match | ||
""" | ||
{ | ||
"type": "object", | ||
"required": [ | ||
"value" | ||
], | ||
"properties": { | ||
"value": { | ||
"type": "array", | ||
"minItems": 0, | ||
"maxItems": 0 | ||
} | ||
} | ||
} | ||
""" | ||
|
||
@issue-10216 | ||
Scenario: user cannot find share if he has deleted the connection | ||
Given using server "LOCAL" | ||
And "Alice" has created the federation share invitation | ||
And using server "REMOTE" | ||
And "Brian" has accepted invitation | ||
And using server "LOCAL" | ||
And user "Alice" has created folder "folderToShare" | ||
And user "Alice" has sent the following resource share invitation to federated user: | ||
| resource | folderToShare | | ||
| space | Personal | | ||
| sharee | Brian | | ||
| shareType | user | | ||
| permissionsRole | Viewer | | ||
| federatedServer | @federation-ocis-server:10200 | | ||
And using server "REMOTE" | ||
When user "Brian" deletes federated connection with user "Alice" using the Graph API | ||
Then the HTTP status code should be "200" | ||
When user "Brian" lists the shares shared with him without retry using the Graph API | ||
Then the HTTP status code should be "200" | ||
And the JSON data of the response should match | ||
""" | ||
{ | ||
"type": "object", | ||
"required": [ | ||
"value" | ||
], | ||
"properties": { | ||
"value": { | ||
"type": "array", | ||
"minItems": 0, | ||
"maxItems": 0, | ||
} | ||
} | ||
} | ||
""" | ||
|
||
@issue-10213 | ||
Scenario: user cannot find share if the user has deleted the connection | ||
Given using server "LOCAL" | ||
And "Alice" has created the federation share invitation | ||
And using server "REMOTE" | ||
And "Brian" has accepted invitation | ||
And using server "LOCAL" | ||
And user "Alice" has created folder "folderToShare" | ||
And user "Alice" has sent the following resource share invitation to federated user: | ||
| resource | folderToShare | | ||
| space | Personal | | ||
| sharee | Brian | | ||
| shareType | user | | ||
| permissionsRole | Viewer | | ||
| federatedServer | @federation-ocis-server:10200 | | ||
When user "Alice" deletes federated connection with user "Brian" using the Graph API | ||
Then the HTTP status code should be "200" | ||
And using server "REMOTE" | ||
When user "Brian" lists the shares shared with him without retry using the Graph API | ||
Then the HTTP status code should be "200" | ||
And the JSON data of the response should match | ||
""" | ||
{ | ||
"type": "object", | ||
"required": [ | ||
"value" | ||
], | ||
"properties": { | ||
"value": { | ||
"type": "array", | ||
"minItems": 0, | ||
"maxItems": 0, | ||
} | ||
} | ||
} | ||
""" |
Oops, something went wrong.