Refactor createShareToShareFolder.feature to use Shares folder

owncloud · Sep 9, 2020 · 1793ba4 · 1793ba4
1 parent afb415a
commit 1793ba4
Show file tree

Hide file tree

Showing 3 changed files with 543 additions and 21 deletions.
diff --git a/tests/acceptance/features/apiShareManagementBasic/createShare.feature b/tests/acceptance/features/apiShareManagementBasic/createShare.feature
@@ -1,4 +1,4 @@
-@api @files_sharing-app-required
+@api @files_sharing-app-required @notToImplementOnOCIS
 Feature: sharing
 
   Background:
@@ -7,7 +7,6 @@ Feature: sharing
 
   @smokeTest
   @skipOnEncryptionType:user-keys @issue-32322
-  @toImplementOnOCIS @issue-ocis-reva-11 @issue-ocis-reva-243
   Scenario Outline: Creating a share of a file with a user, the default permissions are read(1)+update(2)+can-share(16)
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -34,7 +33,6 @@ Feature: sharing
 
   @smokeTest
   @skipOnEncryptionType:user-keys @issue-32322
-  @toImplementOnOCIS @issue-ocis-reva-11 @issue-ocis-reva-243
   Scenario Outline: Creating a share of a file containing commas in the filename, with a user, the default permissions are read(1)+update(2)+can-share(16)
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -60,7 +58,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis-EOS-Storage @issue-ocis-reva-301 @issue-ocis-reva-302
   Scenario Outline: Creating a share of a file with a user and asking for various permission combinations
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -120,7 +117,6 @@ Feature: sharing
       | 1               | 200              |
       | 2               | 400              |
 
-  @skipOnOcis-EOS-Storage @issue-ocis-reva-301
   Scenario Outline: Creating a share of a folder with a user, the default permissions are all permissions(31)
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -145,7 +141,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @issue-ocis-reva-34
   Scenario Outline: Creating a share of a file with a group, the default permissions are read(1)+update(2)+can-share(16)
     Given using OCS API version "<ocs_api_version>"
     And group "grp1" has been created
@@ -169,7 +164,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @issue-ocis-reva-34
   Scenario Outline: Creating a share of a folder with a group, the default permissions are all permissions(31)
     Given using OCS API version "<ocs_api_version>"
     And group "grp1" has been created
@@ -194,7 +188,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @smokeTest @toImplementOnOCIS @issue-ocis-reva-34 @issue-ocis-reva-243
+  @smokeTest
   Scenario Outline: Share of folder to a group
     Given using OCS API version "<ocs_api_version>"
     And these users have been created with default attributes and without skeleton files:
@@ -222,7 +216,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @toImplementOnOCIS @issue-ocis-reva-34 @issue-ocis-reva-243
   Scenario Outline: sharing again an own file while belonging to a group
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -239,7 +232,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @issue-ocis-reva-372 @issue-ocis-reva-243
   Scenario Outline: sharing subfolder of already shared folder, GET result is correct
     Given using OCS API version "<ocs_api_version>"
     And these users have been created with default attributes and without skeleton files:
@@ -269,7 +261,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @toImplementOnOCIS @issue-ocis-reva-14 @issue-ocis-reva-243
   Scenario Outline: user shares a file with file name longer than 64 chars to another user
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -283,7 +274,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @issue-ocis-reva-34 @issue-ocis-reva-243 @toImplementOnOCIS
   Scenario Outline: user shares a file with file name longer than 64 chars to a group
     Given using OCS API version "<ocs_api_version>"
     And group "grp1" has been created
@@ -299,7 +289,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @toImplementOnOCIS @issue-ocis-reva-14 @issue-ocis-reva-243 @issue-ocis-reva-12
   Scenario Outline: user shares a folder with folder name longer than 64 chars to another user
     Given using OCS API version "<ocs_api_version>"
     And user "Brian" has been created with default attributes and without skeleton files
@@ -314,7 +303,6 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @issue-ocis-reva-34 @issue-ocis-reva-243 @issue-ocis-reva-12 @toImplementOnOCIS
   Scenario Outline: user shares a folder with folder name longer than 64 chars to a group
     Given using OCS API version "<ocs_api_version>"
     And group "grp1" has been created
@@ -332,7 +320,6 @@ Feature: sharing
       | 2               | 200             |
 
   @issue-35484
-  @skipOnOcis-OC-Storage @issue-ocis-reva-11
   Scenario: share with user when username contains capital letters
     Given these users have been created without skeleton files:
       | username |
@@ -368,7 +355,6 @@ Feature: sharing
       | /randomfile.txt |
     And the content of file "randomfile.txt" for user "Brian" should be "Random data"
 
-  @issue-ocis-reva-34 @toImplementOnOCIS
   Scenario Outline: Share of folder to a group with emoji in the name
     Given using OCS API version "<ocs_api_version>"
     And these users have been created with default attributes and without skeleton files:
@@ -417,7 +403,7 @@ Feature: sharing
       | 1               |
       | 2               |
 
-  @skipOnLDAP @notToImplementOnOCIS
+  @skipOnLDAP
   # deleting an LDAP group is not relevant or possible using the provisioning API
   Scenario Outline: shares shared to deleted group should not be available
     Given using OCS API version "<ocs_api_version>"
@@ -451,7 +437,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @issue-ocis-reva-34 @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-reva-243 @toImplementOnOCIS
+  @skipOnFilesClassifier @issue-files-classifier-291
   Scenario: Share a file by multiple channels and download from sub-folder and direct file share
     Given these users have been created with default attributes and without skeleton files:
       | username |
@@ -474,7 +460,6 @@ Feature: sharing
       | /common/sub/textfile0.txt |
       | /textfile0.txt            |
 
-  @skipOnOcis-OC-Storage @issue-enterprise-3896 @issue-ocis-reva-243
   Scenario: sharing back to resharer is allowed
     Given these users have been created with default attributes and without skeleton files:
       | username |
@@ -489,7 +474,6 @@ Feature: sharing
 #    Then the HTTP status code should be "405"
     And as "Brian" folder "userOneFolder" should not exist
 
-  @skipOnOcis-OC-Storage @issue-enterprise-3896 @issue-ocis-reva-243
   Scenario: sharing back to original sharer is allowed
     Given these users have been created with default attributes and without skeleton files:
       | username |
@@ -504,7 +488,6 @@ Feature: sharing
 #    Then the HTTP status code should be "405"
     And as "Alice" folder "userOneFolder" should not exist
 
-  @skipOnOcis-OC-Storage @issue-enterprise-3896 @issue-ocis-reva-243
   Scenario: sharing a subfolder to a user that already received parent folder share
     Given these users have been created with default attributes and without skeleton files:
       | username |