Scenarios that are tagged issue-ocis-reva-21 has been reviewed

owncloud · Jul 21, 2020 · 842e450 · 842e450
1 parent cfa0a2a
commit 842e450
Show file tree

Hide file tree

Showing 6 changed files with 229 additions and 40 deletions.
diff --git a/tests/acceptance/features/apiFavorites/favorites.feature b/tests/acceptance/features/apiFavorites/favorites.feature
@@ -86,8 +86,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @smokeTest
-  @skipOnOcis @issue-ocis-reva-21
+  @smokeTest @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-39
   Scenario Outline: Get favorited elements of a folder
     Given using <dav_version> DAV path
     When user "Alice" favorites element "/FOLDER" using the WebDAV API
@@ -103,7 +103,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @skipOnOcis @issue-ocis-reva-21
+  @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-39
   Scenario Outline: Get favorited elements of a subfolder
     Given using <dav_version> DAV path
     And user "Alice" has created folder "/subfolder"
@@ -125,8 +126,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @files_sharing-app-required
-  @skipOnOcis @issue-ocis-reva-21
+  @files_sharing-app-required @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-39
   Scenario Outline: moving a favorite file out of a share keeps favorite state
     Given using <dav_version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
@@ -142,8 +143,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @issue-33840
-  @skipOnOcis @issue-ocis-reva-21
+  @issue-33840 @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-39
   Scenario Outline: Get favorited elements and limit count of entries
     Given using <dav_version> DAV path
     And user "Alice" has favorited element "/textfile0.txt"
@@ -164,8 +165,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @issue-33840
-  @skipOnOcis @issue-ocis-reva-21
+  @issue-33840 @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-39
   Scenario Outline: Get favorited elements paginated in subfolder
     Given using <dav_version> DAV path
     And user "Alice" has created folder "/subfolder"
@@ -194,8 +195,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @files_sharing-app-required
-  @skipOnOcis @issue-ocis-reva-21
+  @files_sharing-app-required @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-39
   Scenario Outline: sharer file favorite state should not change the favorite state of sharee
     Given using <dav_version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
@@ -209,8 +210,8 @@ Feature: favorite
       | old         |
       | new         |
 
-  @files_sharing-app-required
-  @skipOnOcis @issue-ocis-reva-21
+  @files_sharing-app-required @toImplementOnOCIS
+  @skipOnOcis @issue-ocis-reva-243
   Scenario Outline: sharee file favorite state should not change the favorite state of sharer
     Given using <dav_version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files

diff --git a/tests/acceptance/features/apiMain/checksums.feature b/tests/acceptance/features/apiMain/checksums.feature
@@ -60,7 +60,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @skipOnOcis @issue-ocis-reva-98 @issue-ocis-reva-21
+  @skipOnOcis @issue-ocis-reva-98
   Scenario: Downloading a file with checksum should return the checksum in the download header
     Given using old DAV path
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"

diff --git a/tests/acceptance/features/apiShareManagementBasic/createShare.feature b/tests/acceptance/features/apiShareManagementBasic/createShare.feature
@@ -317,7 +317,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243
+  @skipOnOcis @issue-ocis-reva-372 @issue-ocis-reva-243 @toImplementOnOCIS
   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:
@@ -347,6 +347,39 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
+  @skipOnOcV10 @issue-ocis-reva-372 @issue-ocis-reva-243
+  #after fixing all issues delete this Scenario and use the one above
+  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:
+      | username |
+      | Brian    |
+      | Carol    |
+      | David    |
+      | Emily    |
+    And user "Alice" has created folder "/folder1"
+    And user "Alice" has shared folder "/folder1" with user "Brian"
+    And user "Alice" has shared folder "/folder1" with user "Carol"
+    And user "Alice" has created folder "/folder1/folder2"
+    And user "Alice" has shared folder "/folder1/folder2" with user "David"
+    And user "Alice" has shared folder "/folder1/folder2" with user "Emily"
+    When user "Alice" sends HTTP method "GET" to OCS API endpoint "/apps/files_sharing/api/v1/shares"
+    Then the OCS status code should be "<ocs_status_code>"
+    And the HTTP status code should be "200"
+    And the response should contain 4 entries
+    And folder "/folder1" should be included as path in the response
+    And folder "/folder2" should be included as path in the response
+#    And folder "/folder1/folder2" should be included as path in the response
+    And user "Alice" sends HTTP method "GET" to OCS API endpoint "/apps/files_sharing/api/v1/shares?path=/folder1/folder2"
+    And the response should contain 2 entries
+    And folder "/folder1" should not be included as path in the response
+    And folder "/folder2" should be included as path in the response
+#    And folder "/folder1/folder2" should be included as path in the response
+    Examples:
+      | ocs_api_version | ocs_status_code |
+      | 1               | 100             |
+      | 2               | 200             |
+
   @skipOnOcis @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>"
@@ -361,7 +394,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243
+  @skipOnOcis @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
@@ -392,7 +425,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243 @issue-ocis-reva-12
+  @skipOnOcis @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
@@ -446,7 +479,7 @@ Feature: sharing
       | /randomfile.txt |
     And the content of file "randomfile.txt" for user "Brian" should be "Random data"
 
-  @skipOnOcis @issue-ocis-reva-21
+  @skipOnOcis @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:
@@ -529,7 +562,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis @issue-ocis-reva-21 @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-reva-243
+  @skipOnOcis @issue-ocis-reva-34 @skipOnFilesClassifier @issue-files-classifier-291 @issue-ocis-reva-243 @toImplementOnOCIS
   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 |

diff --git a/tests/acceptance/features/apiShareOperations/accessToShare.feature b/tests/acceptance/features/apiShareOperations/accessToShare.feature
@@ -34,7 +34,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @smokeTest @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243
+  @smokeTest @skipOnOcis @issue-ocis-reva-260
   Scenario Outline: Sharee can't see the share that is filtered out
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
@@ -48,7 +48,22 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @smokeTest @skipOnOcis @issue-ocis-reva-21 @issue-ocis-reva-243
+  @smokeTest @skipOnOcV10 @issue-ocis-reva-260
+  #after fixing the issues delete this Scenario and use the one above
+  Scenario Outline: Sharee can't see the share that is filtered out
+    Given using OCS API version "<ocs_api_version>"
+    And user "Alice" has shared file "textfile0.txt" with user "Brian"
+    And user "Alice" has shared file "textfile1.txt" with user "Brian"
+    When user "Brian" gets all the shares shared with him that are received as file "textfile0 (2).txt" using the provisioning API
+    Then the OCS status code should be "<ocs_status_code>"
+    And the HTTP status code should be "200"
+    And the last share_id should be included in the response
+    Examples:
+      | ocs_api_version | ocs_status_code |
+      | 1               | 100             |
+      | 2               | 200             |
+
+  @smokeTest @skipOnOcis @issue-ocis-reva-34 @issue-ocis-reva-194
   Scenario Outline: Sharee can see the group share
     Given using OCS API version "<ocs_api_version>"
     And group "grp1" has been created

diff --git a/tests/acceptance/features/apiShareOperations/gettingShares.feature b/tests/acceptance/features/apiShareOperations/gettingShares.feature
@@ -54,7 +54,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis @smokeTest @issue-ocis-reva-243 @issue-ocis-reva-21
+  @skipOnOcis @smokeTest @issue-ocis-reva-243
   Scenario Outline: getting all shares of a file with reshares
     Given using OCS API version "<ocs_api_version>"
     And these users have been created with default attributes and skeleton files:
@@ -155,7 +155,7 @@ Feature: sharing
       | 1               | 100             |
       | 2               | 200             |
 
-  @skipOnOcis @issue-ocis-reva-21
+  @skipOnOcis @issue-ocis-reva-374
   Scenario Outline: Get a share with a user that didn't receive the share
     Given using OCS API version "<ocs_api_version>"
     And user "Carol" has been created with default attributes and without skeleton files
@@ -168,6 +168,21 @@ Feature: sharing
       | 1               | 200              |
       | 2               | 404              |
 
+  @skipOnOcV10 @issue-ocis-reva-374
+  #after fixing all issues delete this Scenario and use the one above
+  Scenario Outline: Get a share with a user that didn't receive the share
+    Given using OCS API version "<ocs_api_version>"
+    And user "Carol" has been created with default attributes and without skeleton files
+    And user "Alice" has shared file "textfile0.txt" with user "Brian"
+    When user "Carol" gets the info of the last share using the sharing API
+    Then the OCS status code should be "400"
+#    Then the OCS status code should be "404"
+    And the HTTP status code should be "<http_status_code>"
+    Examples:
+      | ocs_api_version | http_status_code |
+      | 1               | 200              |
+      | 2               | 400              |
+
   @skipOnLDAP @skipOnOcis @issue-ocis-reva-194
   Scenario: Share of folder to a group, remove user from that group
     Given using OCS API version "1"
@@ -191,7 +206,7 @@ Feature: sharing
       | /PARENT%20(2)/           |
       | /PARENT%20(2)/parent.txt |
 
-  @skipOnOcis @issue-ocis-reva-21
+  @skipOnOcis @issue-ocis-reva-372
   Scenario Outline: getting all the shares inside the folder
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "PARENT/parent.txt" with user "Brian"
@@ -203,3 +218,17 @@ Feature: sharing
       | ocs_api_version | ocs_status_code |
       | 1               | 100             |
       | 2               | 200             |
+
+  @skipOnOcV10 @issue-ocis-reva-372
+  #after fixing all issues delete this Scenario and use the one above
+  Scenario Outline: getting all the shares inside the folder
+    Given using OCS API version "<ocs_api_version>"
+    And user "Alice" has shared file "PARENT/parent.txt" with user "Brian"
+    When user "Alice" gets all the shares inside the folder "PARENT/parent.txt" using the sharing API
+    Then the OCS status code should be "<ocs_status_code>"
+    And the HTTP status code should be "200"
+    And file "parent.txt" should be included in the response
+    Examples:
+      | ocs_api_version | ocs_status_code |
+      | 1               | 100             |
+      | 2               | 200             |