sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Skip local tests on OCIS storage

Browse Source
This commit is contained in:
Phil Davis
2020-09-13 09:14:22 +05:45
parent 7ce9cd58b8
commit b953b5e546
13 changed files with 28 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/apiOcisSpecific/apiFavorites-favorites.feature
+1 -1
View File
@@ -13,7 +13,7 @@ Feature: favorite
And user "Alice" has created folder "/PARENT"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@skipOnOcis-OC-Storage @issue-ocis-reva-276
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-276
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Favorite a folder
Given using <dav_version> DAV path
tests/acceptance/features/apiOcisSpecific/apiShareManagementBasic-createShare.feature
+3 -3
View File
@@ -5,7 +5,7 @@ Feature: sharing
Given user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
@skipOnOcis-OC-Storage @issue-ocis-reva-301 @issue-ocis-reva-302
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-301 @issue-ocis-reva-302
# after fixing all issues delete this Scenario and use the one from oC10 core
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>"
@@ -56,7 +56,7 @@ Feature: sharing
| 1 | 200 | 500 |
| 2 | 200 | 500 |
@skipOnOcis-OC-Storage @issue-ocis-reva-301 @issue-ocis-reva-302
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-301 @issue-ocis-reva-302
# after fixing all issues delete this Scenario and use the one from oC10 core
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>"
@@ -83,7 +83,7 @@ Feature: sharing
| 1 | 100 |
| 2 | 200 |
@issue-ocis-reva-372 @issue-ocis-reva-243
@issue-ocis-reva-372 @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: sharing subfolder of already shared folder, GET result is correct
Given using OCS API version "<ocs_api_version>"
tests/acceptance/features/apiOcisSpecific/apiSharePublicLink1-createPublicLinkShare.feature
+2 -2
View File
@@ -5,7 +5,7 @@ Feature: create a public link share
Background:
Given user "Alice" has been created with default attributes and skeleton files
@issue-37605
@issue-37605 @skipOnOcis-OCIS-Storage
# after fixing all issues make the oC10 scenario like this one, and delete this scenario
Scenario: Get the mtime of a file inside a folder shared by public link using new webDAV version (run on OCIS)
Given user "Alice" has created folder "testFolder"
@@ -17,7 +17,7 @@ Feature: create a public link share
And as "Alice" the mtime of the file "testFolder/file.txt" should be "Thu, 08 Aug 2019 04:18:13 GMT"
And the mtime of file "file.txt" in the last shared public link using the WebDAV API should be "Thu, 08 Aug 2019 04:18:13 GMT"
@issue-37605
@issue-37605 @skipOnOcis-OCIS-Storage
# after fixing all issues make the oC10 scenario like this one, and delete this scenario
Scenario: overwriting a file changes its mtime (new public webDAV API) (run on OCIS)
Given user "Alice" has created folder "testFolder"
tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-copyFromPublicLink.feature
+4 -4
View File
@@ -6,7 +6,7 @@ Feature: copying from public link share
And user "Alice" has created folder "/PARENT"
And the administrator has enabled DAV tech_preview
@issue-ocis-reva-373 @issue-core-37683
@issue-ocis-reva-373 @issue-core-37683 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Copy folder within a public link folder to the same folder name as an already existing file
Given user "Alice" has created folder "/PARENT/testFolder"
@@ -22,7 +22,7 @@ Feature: copying from public link share
And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data"
And the content of file "/PARENT/copy1.txt" for user "Alice" should be "some data 1"
@issue-ocis-reva-373 @issue-core-37683
@issue-ocis-reva-373 @issue-core-37683 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Copy file within a public link folder to a file with name same as an existing folder
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
@@ -37,7 +37,7 @@ Feature: copying from public link share
And as "Alice" file "/PARENT/new-folder" should exist
And the content of file "/PARENT/testfile.txt" for user "Alice" should be "some data"
@issue-ocis-reva-368
@issue-ocis-reva-368 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Copy file within a public link folder to a file with unusual destination names
Given user "Alice" has uploaded file with content "some data" to "/PARENT/testfile.txt"
@@ -53,7 +53,7 @@ Feature: copying from public link share
| testfile.txt |
| |
@issue-ocis-reva-368
@issue-ocis-reva-368 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Copy folder within a public link folder to a folder with unusual destination names
Given user "Alice" has created folder "/PARENT/testFolder"
tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature
+2 -2
View File
@@ -5,7 +5,7 @@ Feature: sharing
Given using OCS API version "1"
And user "Alice" has been created with default attributes and skeleton files
@skipOnOcis-EOS-Storage @toFixOnOCIS @issue-ocis-reva-243
@skipOnOcis-EOS-Storage @toFixOnOCIS @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Share ownership change after moving a shared file to another share
Given these users have been created with default attributes and without skeleton files:
@@ -43,7 +43,7 @@ Feature: sharing
And as "Alice" folder "/Alice-folder/folder2" should exist
And as "Carol" folder "/Carol-folder/folder2" should not exist
@skipOnOcis-OC-Storage @toFixOnOCIS @issue-ocis-reva-243
@skipOnOcis-OC-Storage @toFixOnOCIS @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
# same as oC10 core Scenario but without displayname_owner because EOS does not report it
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Share ownership change after moving a shared file to another share
tests/acceptance/features/apiOcisSpecific/apiTrashbin-trashbinDelete.feature
+1
View File
@@ -40,6 +40,7 @@ Feature: files and folders can be deleted from the trashbin
@smokeTest
@issue-ocis-reva-118
@issue-product-179
@skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: delete a single file from the trashbin
Given user "Alice" has deleted file "/textfile0.txt"
tests/acceptance/features/apiOcisSpecific/apiWebdavMove1-moveFolderToBlacklistedName.feature
+1 -1
View File
@@ -8,7 +8,7 @@ Feature: users cannot move (rename) a folder to a blacklisted name
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@issue-ocis-reva-211 @skipOnOcis-EOS-Storage @issue-ocis-reva-269
@issue-ocis-reva-211 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-269
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Renaming a folder to a name that is banned by default is allowed
Given using <dav_version> DAV path
tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature
+3 -3
View File
@@ -8,7 +8,7 @@ Feature: move (rename) file
Given using OCS API version "1"
And user "Alice" has been created with default attributes and skeleton files
@issue-ocis-reva-211
@issue-ocis-reva-211 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: rename a file into an invalid filename
Given using <dav_version> DAV path
@@ -20,7 +20,7 @@ Feature: move (rename) file
| old |
| new |
@issue-ocis-reva-211
@issue-ocis-reva-211 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Renaming a file to a path with extension .part is possible
Given using <dav_version> DAV path
@@ -32,7 +32,7 @@ Feature: move (rename) file
| old |
| new |
@skipOnOcis-OC-Storage @issue-ocis-reva-211
@skipOnOcis-OC-Storage @issue-ocis-reva-211 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: renaming to a file with special characters
When user "Alice" moves file "/textfile0.txt" to "/<renamed_file>" using the WebDAV API
tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFileToBlacklistedName.feature
+1 -1
View File
@@ -8,7 +8,7 @@ Feature: users cannot move (rename) a file to a blacklisted name
Given using OCS API version "1"
And user "Alice" has been created with default attributes and skeleton files
@issue-ocis-reva-211
@issue-ocis-reva-211 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: rename a file to a filename that is banned by default
Given using <dav_version> DAV path
tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-createFolder.feature
+1 -1
View File
@@ -8,7 +8,7 @@ Feature: create folder
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@issue-ocis-reva-168 @skipOnOcis-EOS-Storage
@issue-ocis-reva-168 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: try to create a folder that already exists
Given using <dav_version> DAV path
tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature
+1 -1
View File
@@ -8,7 +8,7 @@ Feature: set file properties
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@skipOnOcis-OC-Storage @issue-ocis-reva-276
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-276
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Setting custom DAV property
Given using <dav_version> DAV path
tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature
+6 -6
View File
@@ -8,7 +8,7 @@ Feature: get file properties
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@issue-ocis-reva-214
@issue-ocis-reva-214 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Do a PROPFIND of various file names
Given using <dav_version> DAV path
@@ -25,7 +25,7 @@ Feature: get file properties
| new | /file #2.txt | dav\/files\/%username%\/file%20%232\.txt |
| new | /file &2.txt | dav\/files\/%username%\/file%20&2\.txt |
@issue-ocis-reva-214 @issue-ocis-reva-265 @skipOnOcis-EOS-Storage
@issue-ocis-reva-214 @issue-ocis-reva-265 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Do a PROPFIND of various file names
Given using <dav_version> DAV path
@@ -38,7 +38,7 @@ Feature: get file properties
| old | /file ?2.txt | webdav\/file%20%3F2\.txt |
| new | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt |
@skipOnOcis-OC-Storage @issue-ocis-reva-265
@skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: upload a file to content
Given using <dav_version> DAV path
@@ -49,7 +49,7 @@ Feature: get file properties
| old | /file ?2.txt |
| new | /file ?2.txt |
@issue-ocis-reva-214
@issue-ocis-reva-214 @skipOnOcis-OCIS-Storage @issue-ocis-reva-471
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
@@ -75,7 +75,7 @@ Feature: get file properties
| new | /folder #2.txt | dav\/files\/%username%\/folder%20%232\.txt |
| new | /folder &2.txt | dav\/files\/%username%\/folder%20&2\.txt |
@issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265
@issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage @issue-ocis-reva-471
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
@@ -91,7 +91,7 @@ Feature: get file properties
| old | /folder ?2.txt | webdav\/folder%20%3F2\.txt |
| new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt |
@skipOnOcis-OC-Storage @issue-ocis-reva-265
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-265
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path
tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature
+2 -2
View File
@@ -8,7 +8,7 @@ Feature: upload file
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@skipOnOcis-OC-Storage @issue-ocis-reva-265
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-265
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: upload a file and check download content
Given using <dav_version> DAV path
@@ -19,7 +19,7 @@ Feature: upload file
| old | "file ?2.txt" |
| new | "file ?2.txt" |
@skipOnOcis-OC-Storage @issue-product-127
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-product-127
# this scenario passes/fails intermittently on OC storage, so do not run it in CI
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: uploading a file inside a folder changes its etag