removed scenario related to federated share

owncloud · Jun 16, 2023 · dc6211f · dc6211f
1 parent cdb3a48
commit dc6211f
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 44 deletions.
diff --git a/tests/acceptance/expected-failures-API-on-OCIS-storage.md b/tests/acceptance/expected-failures-API-on-OCIS-storage.md
@@ -155,11 +155,6 @@ Synchronization features like etag propagation, setting mtime and locking files
 
 File and sync features in a shared scenario
 
-#### [federation share is not implement in ocis] (https://github.com/owncloud/ocis/issues/1329)
-
-- [coreApiSharees/sharees.feature:180](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L180)
-- [coreApiSharees/sharees.feature:181](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L181)
-
 #### [accepting matching name shared resources from different users/groups sets no serial identifiers on the resource name for the receiver](https://github.com/owncloud/ocis/issues/4289)
 
 - [coreApiShareManagementToShares/acceptShares.feature:238](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L238)

diff --git a/tests/acceptance/features/coreApiSharees/sharees.feature b/tests/acceptance/features/coreApiSharees/sharees.feature
@@ -161,45 +161,6 @@ Feature: search sharees
       | 2               | 200        | 200         |
 
 
-  Scenario Outline: federated sharee for files
-    Given using OCS API version "<ocs-api-version>"
-    When user "Alice" gets the sharees using the sharing API with parameters
-      | search   | test@localhost |
-      | itemType | file           |
-    Then the OCS status code should be "<ocs-status>"
-    And the HTTP status code should be "<http-status>"
-    And the "exact users" sharees returned should be empty
-    And the "users" sharees returned should be empty
-    And the "exact groups" sharees returned should be empty
-    And the "groups" sharees returned should be empty
-    And the "exact remotes" sharees returned should be
-      | test@localhost | 6 | test@localhost |
-    And the "remotes" sharees returned should be empty
-    Examples:
-      | ocs-api-version | ocs-status | http-status |
-      | 1               | 100        | 200         |
-      | 2               | 200        | 200         |
-
-
-  Scenario Outline: federated sharee for calendars not allowed
-    Given using OCS API version "<ocs-api-version>"
-    When user "Alice" gets the sharees using the sharing API with parameters
-      | search   | test@localhost |
-      | itemType | calendar       |
-    Then the OCS status code should be "<ocs-status>"
-    And the HTTP status code should be "<http-status>"
-    And the "exact users" sharees returned should be empty
-    And the "users" sharees returned should be empty
-    And the "exact groups" sharees returned should be empty
-    And the "groups" sharees returned should be empty
-    And the "exact remotes" sharees returned should be empty
-    And the "remotes" sharees returned should be empty
-    Examples:
-      | ocs-api-version | ocs-status | http-status |
-      | 1               | 100        | 200         |
-      | 2               | 200        | 200         |
-
-
   Scenario Outline: enumerate only group members - only show partial results from member of groups
     Given using OCS API version "<ocs-api-version>"
     And these users have been created with default attributes and without skeleton files: