mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-07-14 17:42:03 -04:00
Removed scenarios, system configuration setting is not available
This commit is contained in:
Prarup Gurung
@@ -232,19 +232,6 @@ cannot share a folder with create permission
|
||||
|
||||
- [coreApiWebdavPreviews/previews.feature:101](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L101)
|
||||
|
||||
#### [Requesting a file preview when it is disabled by the administrator](https://github.com/owncloud/ocis/issues/192)
|
||||
|
||||
- [coreApiWebdavPreviews/previews.feature:116](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L116)
|
||||
|
||||
#### [Cannot set/unset maximum and minimum preview dimensions](https://github.com/owncloud/ocis/issues/2070)
|
||||
|
||||
- [coreApiWebdavPreviews/previews.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L123)
|
||||
- [coreApiWebdavPreviews/previews.feature:145](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L145)
|
||||
- [coreApiWebdavPreviews/previews.feature:146](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L146)
|
||||
- [coreApiWebdavPreviews/previews.feature:147](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L147)
|
||||
- [coreApiWebdavPreviews/previews.feature:157](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L157)
|
||||
- [coreApiWebdavPreviews/previews.feature:158](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L158)
|
||||
|
||||
#### [copying a folder within a public link folder to folder with same name as an already existing file overwrites the parent file](https://github.com/owncloud/ocis/issues/1232)
|
||||
|
||||
- [coreApiSharePublicLink2/copyFromPublicLink.feature:63](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink2/copyFromPublicLink.feature#L63)
|
||||
@@ -618,18 +605,6 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
|
||||
- _The `OC-LazyOps` header is [no longer supported by the client](https://github.com/owncloud/client/pull/8398), implementing this is not necessary for a first production release. We plan to have an upload state machine to visualize the state of a file, see https://github.com/owncloud/ocis/issues/214_
|
||||
- _Blacklisted ignored files are no longer required because ocis can handle `.htaccess` files without security implications introduced by serving user provided files with apache._
|
||||
|
||||
#### [uploading with old-chunking does not work](https://github.com/owncloud/ocis/issues/1343)
|
||||
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:19](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L19)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:20](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L20)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L25)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:37](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L37)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L38)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:43](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L43)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L75)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:76](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L76)
|
||||
- [coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature:81](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToExcludedDirectory.feature#L81)
|
||||
|
||||
#### [Blacklist files extensions](https://github.com/owncloud/ocis/issues/2177)
|
||||
|
||||
- [coreApiWebdavProperties1/copyFile.feature:119](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L119)
|
||||
@@ -641,15 +616,6 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
|
||||
- [coreApiWebdavUpload1/uploadFile.feature:181](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature#L181)
|
||||
- [coreApiWebdavUpload1/uploadFile.feature:182](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature#L182)
|
||||
- [coreApiWebdavUpload1/uploadFile.feature:187](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFile.feature#L187)
|
||||
- [coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:13](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature#L13)
|
||||
- [coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature#L25)
|
||||
- [coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature#L26)
|
||||
- [coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature#L27)
|
||||
- [coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:13](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature#L13)
|
||||
- [coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:19](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature#L19)
|
||||
- [coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature#L33)
|
||||
- [coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:34](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature#L34)
|
||||
- [coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature#L35)
|
||||
- [coreApiWebdavMove2/moveFile.feature:176](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature#L176)
|
||||
- [coreApiWebdavMove2/moveFile.feature:177](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature#L177)
|
||||
- [coreApiWebdavMove2/moveFile.feature:182](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature#L182)
|
||||
@@ -659,49 +625,12 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:21](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L21)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:22](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L22)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L27)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:39](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L39)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:40](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L40)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:45](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L45)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:77](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L77)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:78](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L78)
|
||||
- [coreApiWebdavMove1/moveFolderToBlacklistedName.feature:83](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToBlacklistedName.feature#L83)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:19](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L19)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:20](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L20)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:34](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L34)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L35)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:70](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L70)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:71](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L71)
|
||||
|
||||
#### [cannot set excluded directories](https://github.com/owncloud/product/issues/261)
|
||||
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:21](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L21)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:22](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L22)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L27)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:40](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L40)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:41](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L41)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:46](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L46)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:79](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L79)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:80](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L80)
|
||||
- [coreApiWebdavMove1/moveFolderToExcludedDirectory.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolderToExcludedDirectory.feature#L85)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:19](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L19)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:20](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L20)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L35)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:36](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L36)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L73)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L74)
|
||||
|
||||
#### [system configuration options missing](https://github.com/owncloud/ocis/issues/1323)
|
||||
|
||||
- [coreApiWebdavUpload1/uploadFileToBlacklistedName.feature:19](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToBlacklistedName.feature#L19)
|
||||
- [coreApiWebdavUpload1/uploadFileToBlacklistedName.feature:20](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToBlacklistedName.feature#L20)
|
||||
- [coreApiWebdavUpload1/uploadFileToBlacklistedName.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToBlacklistedName.feature#L25)
|
||||
- [coreApiWebdavUpload1/uploadFileToBlacklistedName.feature:56](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToBlacklistedName.feature#L56)
|
||||
- [coreApiWebdavUpload1/uploadFileToBlacklistedName.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToBlacklistedName.feature#L55)
|
||||
- [coreApiWebdavUpload1/uploadFileToBlacklistedName.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUpload1/uploadFileToBlacklistedName.feature#L61)
|
||||
|
||||
#### [Preview of text file with UTF content does not render correctly](https://github.com/owncloud/ocis/issues/2570)
|
||||
|
||||
- [coreApiWebdavPreviews/previews.feature:181](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L181)
|
||||
- [coreApiWebdavPreviews/previews.feature:136](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L136)
|
||||
|
||||
#### [Share path in the response is different between share states](https://github.com/owncloud/ocis/issues/2540)
|
||||
|
||||
@@ -742,8 +671,6 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
|
||||
- [coreApiWebdavMove1/moveFolder.feature:63](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove1/moveFolder.feature#L63)
|
||||
- [coreApiWebdavMove2/moveFile.feature:138](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFile.feature#L138)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L25)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:40](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L40)
|
||||
- [coreApiWebdavMove2/moveFileToBlacklistedName.feature:76](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToBlacklistedName.feature#L76)
|
||||
|
||||
#### [REPORT method on spaces returns an incorrect d:href response](https://github.com/owncloud/ocis/issues/3111)
|
||||
|
||||
@@ -762,12 +689,6 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
|
||||
- [coreApiWebdavOperations/listFiles.feature:408](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature#L408)
|
||||
- [coreApiWebdavOperations/listFiles.feature:413](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavOperations/listFiles.feature#L413)
|
||||
|
||||
#### [Renaming resource to excluded directory name is allowed in spaces webdav](https://github.com/owncloud/ocis/issues/3102)
|
||||
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L25)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:41](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L41)
|
||||
- [coreApiWebdavMove2/moveFileToExcludedDirectory.feature:79](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveFileToExcludedDirectory.feature#L79)
|
||||
|
||||
### [graph/users: enable/disable users](https://github.com/owncloud/ocis/issues/3064)
|
||||
|
||||
- [coreApiWebdavOperations/refuseAccess.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature#L35)
|
||||
|
||||
@@ -245,51 +245,3 @@ Feature: sharees
|
||||
| ocs-api-version | ocs-status | http-status |
|
||||
| 1 | 100 | 200 |
|
||||
| 2 | 200 | 200 |
|
||||
|
||||
|
||||
Scenario Outline: search for sharees when search min length is set to 2
|
||||
Given user "sharee2" has been created with default attributes and without skeleton files
|
||||
And using OCS API version "<ocs-api-version>"
|
||||
When user "sharee1" gets the sharees using the sharing API with parameters
|
||||
| search | sh |
|
||||
| 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 include
|
||||
| Sharee One | 0 | sharee1 |
|
||||
| Sharee Two | 0 | sharee2 |
|
||||
And the "exact groups" sharees returned should be empty
|
||||
And the "groups" sharees returned should include
|
||||
| ShareeGroup | 1 | ShareeGroup |
|
||||
| ShareeGroup2 | 1 | ShareeGroup2 |
|
||||
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: search for sharees with long name when search min length is set to 2
|
||||
Given user "sharee2" has been created with default attributes and without skeleton files
|
||||
And using OCS API version "<ocs-api-version>"
|
||||
When user "sharee1" gets the sharees using the sharing API with parameters
|
||||
| search | sharee |
|
||||
| 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 include
|
||||
| Sharee One | 0 | sharee1 |
|
||||
| Sharee Two | 0 | sharee2 |
|
||||
And the "exact groups" sharees returned should be empty
|
||||
And the "groups" sharees returned should include
|
||||
| ShareeGroup | 1 | ShareeGroup |
|
||||
| ShareeGroup2 | 1 | ShareeGroup2 |
|
||||
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 |
|
||||
|
||||
@@ -25,59 +25,3 @@ Feature: users cannot move (rename) a folder to a blacklisted name
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: Rename a folder to a banned name
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/blacklisted-file.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare/ |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a folder to a folder name that matches (or not) blacklisted_files_regex
|
||||
Given using <dav_version> DAV path
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Brian" has created folder "/testshare"
|
||||
And user "Brian" has created folder "/FOLDER"
|
||||
When user "Brian" moves folder "/testshare" to these foldernames using the webDAV API then the results should be as listed
|
||||
| foldername | http-code | exists |
|
||||
| .ext | 403 | no |
|
||||
| filename.ext | 403 | no |
|
||||
| bannedfilename.txt | 403 | no |
|
||||
| containsbannedstring | 403 | no |
|
||||
| this-ContainsBannedString.txt | 403 | no |
|
||||
| /FOLDER/.ext | 403 | no |
|
||||
| /FOLDER/filename.ext | 403 | no |
|
||||
| /FOLDER/bannedfilename.txt | 403 | no |
|
||||
| /FOLDER/containsbannedstring | 403 | no |
|
||||
| /FOLDER/this-ContainsBannedString.txt | 403 | no |
|
||||
| .extension | 201 | yes |
|
||||
| filename.txt | 201 | yes |
|
||||
| bannedfilename | 201 | yes |
|
||||
| bannedfilenamewithoutdot | 201 | yes |
|
||||
| not-contains-banned-string.txt | 201 | yes |
|
||||
| /FOLDER/.extension | 201 | yes |
|
||||
| /FOLDER/filename.txt | 201 | yes |
|
||||
| /FOLDER/bannedfilename | 201 | yes |
|
||||
| /FOLDER/bannedfilenamewithoutdot | 201 | yes |
|
||||
| /FOLDER/not-contains-banned-string.txt | 201 | yes |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@@ -1,85 +0,0 @@
|
||||
@api @issue-ocis-reva-14
|
||||
Feature: users cannot move (rename) a folder to or into an excluded directory
|
||||
As an administrator
|
||||
I want to be able to exclude directories (folders) from being processed. Any attempt to rename an existing folder to one of those names should be refused.
|
||||
So that I can have directories on my cloud server storage that are not available for syncing.
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
|
||||
Scenario Outline: Rename a folder to an excluded directory name
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/.github" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare/ |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: Rename a folder to an excluded directory name inside a parent directory
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
When user "Alice" moves folder "/testshare" to "/FOLDER/.github" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And user "Alice" should see the following elements
|
||||
| /testshare/ |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a folder to a folder name that matches (or not) excluded_directories_regex
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
When user "Alice" moves folder "/testshare" to these foldernames using the webDAV API then the results should be as listed
|
||||
| foldername | http-code | exists |
|
||||
| endswith.bad | 403 | no |
|
||||
| thisendswith.bad | 403 | no |
|
||||
| .git | 403 | no |
|
||||
| .github | 403 | no |
|
||||
| containsvirusinthename | 403 | no |
|
||||
| this-containsvirusinthename.txt | 403 | no |
|
||||
| /FOLDER/endswith.bad | 403 | no |
|
||||
| /FOLDER/thisendswith.bad | 403 | no |
|
||||
| /FOLDER/.git | 403 | no |
|
||||
| /FOLDER/.github | 403 | no |
|
||||
| /FOLDER/containsvirusinthename | 403 | no |
|
||||
| /FOLDER/this-containsvirusinthename.txt | 403 | no |
|
||||
| endswith.badandotherstuff | 201 | yes |
|
||||
| thisendswith.badandotherstuff | 201 | yes |
|
||||
| name.git | 201 | yes |
|
||||
| name.github | 201 | yes |
|
||||
| not-contains-virus-in-the-name.txt | 201 | yes |
|
||||
| /FOLDER/endswith.badandotherstuff | 201 | yes |
|
||||
| /FOLDER/thisendswith.badandotherstuff | 201 | yes |
|
||||
| /FOLDER/name.git | 201 | yes |
|
||||
| /FOLDER/name.github | 201 | yes |
|
||||
| /FOLDER/not-contains-virus-in-the-name.txt | 201 | yes |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
@@ -23,54 +23,3 @@ Feature: users cannot move (rename) a file to a blacklisted name
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a file to a banned filename
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" moves file "/textfile0.txt" to "/blacklisted-file.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a file to a filename that matches (or not) blacklisted_files_regex
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" moves file "/textfile0.txt" to these filenames using the webDAV API then the results should be as listed
|
||||
| filename | http-code | exists |
|
||||
| .ext | 403 | no |
|
||||
| filename.ext | 403 | no |
|
||||
| bannedfilename.txt | 403 | no |
|
||||
| containsbannedstring | 403 | no |
|
||||
| this-ContainsBannedString.txt | 403 | no |
|
||||
| /FOLDER/.ext | 403 | no |
|
||||
| /FOLDER/filename.ext | 403 | no |
|
||||
| /FOLDER/bannedfilename.txt | 403 | no |
|
||||
| /FOLDER/containsbannedstring | 403 | no |
|
||||
| /FOLDER/this-ContainsBannedString.txt | 403 | no |
|
||||
| .extension | 201 | yes |
|
||||
| filename.txt | 201 | yes |
|
||||
| bannedfilename | 201 | yes |
|
||||
| bannedfilenamewithoutdot | 201 | yes |
|
||||
| not-contains-banned-string.txt | 201 | yes |
|
||||
| /FOLDER/.extension | 201 | yes |
|
||||
| /FOLDER/filename.txt | 201 | yes |
|
||||
| /FOLDER/bannedfilename | 201 | yes |
|
||||
| /FOLDER/bannedfilenamewithoutdot | 201 | yes |
|
||||
| /FOLDER/not-contains-banned-string.txt | 201 | yes |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@@ -1,79 +0,0 @@
|
||||
@api @issue-ocis-reva-14
|
||||
Feature: users cannot move (rename) a file to or into an excluded directory
|
||||
As an administrator
|
||||
I want to be able to exclude directories (folders) from being processed. Any attempt to rename an existing file to one of those names should be refused.
|
||||
So that I can have directories on my cloud server storage that are not available for syncing.
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And 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"
|
||||
|
||||
|
||||
Scenario Outline: rename a file to an excluded directory name
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" moves file "/textfile0.txt" to "/.github" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a file to an excluded directory name inside a parent directory
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" moves file "/textfile0.txt" to "/FOLDER/.github" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
|
||||
Scenario Outline: rename a file to a filename that matches (or not) excluded_directories_regex
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" moves file "/textfile0.txt" to these filenames using the webDAV API then the results should be as listed
|
||||
| filename | http-code | exists |
|
||||
| endswith.bad | 403 | no |
|
||||
| thisendswith.bad | 403 | no |
|
||||
| .git | 403 | no |
|
||||
| .github | 403 | no |
|
||||
| containsvirusinthename | 403 | no |
|
||||
| this-containsvirusinthename.txt | 403 | no |
|
||||
| /FOLDER/endswith.bad | 403 | no |
|
||||
| /FOLDER/thisendswith.bad | 403 | no |
|
||||
| /FOLDER/.git | 403 | no |
|
||||
| /FOLDER/.github | 403 | no |
|
||||
| /FOLDER/containsvirusinthename | 403 | no |
|
||||
| /FOLDER/this-containsvirusinthename.txt | 403 | no |
|
||||
| endswith.badandotherstuff | 201 | yes |
|
||||
| thisendswith.badandotherstuff | 201 | yes |
|
||||
| name.git | 201 | yes |
|
||||
| name.github | 201 | yes |
|
||||
| not-contains-virus-in-the-name.txt | 201 | yes |
|
||||
| /FOLDER/endswith.badandotherstuff | 201 | yes |
|
||||
| /FOLDER/thisendswith.badandotherstuff | 201 | yes |
|
||||
| /FOLDER/name.git | 201 | yes |
|
||||
| /FOLDER/name.github | 201 | yes |
|
||||
| /FOLDER/not-contains-virus-in-the-name.txt | 201 | yes |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
@@ -113,51 +113,6 @@ Feature: previews of files downloaded through the webdav API
|
||||
And the value of the item "/d:error/s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound"
|
||||
|
||||
|
||||
Scenario: Download file previews when it is disabled by the administrator
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When user "Alice" downloads the preview of "/parent.txt" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "404"
|
||||
And the value of the item "/d:error/s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound"
|
||||
|
||||
|
||||
Scenario: unset maximum size of previews
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When user "Alice" downloads the preview of "/parent.txt" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "404"
|
||||
And the value of the item "/d:error/s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound"
|
||||
|
||||
|
||||
Scenario: download preview of size "null"
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When user "Alice" downloads the preview of "/parent.txt" with width "null" and height "null" using the WebDAV API
|
||||
Then the HTTP status code should be "400"
|
||||
And the value of the item "/d:error/s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\BadRequest"
|
||||
|
||||
|
||||
Scenario Outline: download previews of different size smaller than the maximum size set
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When user "Alice" downloads the preview of "/parent.txt" with width "<width>" and height "<height>" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
And the downloaded image should be "<width>" pixels wide and "<height>" pixels high
|
||||
Examples:
|
||||
| width | height |
|
||||
| 32 | 32 |
|
||||
| 12 | 12 |
|
||||
| 32 | 12 |
|
||||
| 12 | 32 |
|
||||
|
||||
|
||||
Scenario Outline: download previews of different size larger than the maximum size set
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When user "Alice" downloads the preview of "/parent.txt" with width "<width>" and height "<height>" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
And the downloaded image should be "32" pixels wide and "32" pixels high
|
||||
Examples:
|
||||
| width | height |
|
||||
| 64 | 64 |
|
||||
| 2048 | 2048 |
|
||||
|
||||
|
||||
Scenario: preview content changes with the change in file content
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
And user "Alice" has downloaded the preview of "/parent.txt" with width "32" and height "32"
|
||||
|
||||
@@ -1,61 +0,0 @@
|
||||
@api
|
||||
Feature: users cannot upload a file to a blacklisted name
|
||||
As an administrator
|
||||
I want to be able to prevent users from uploading files to specified file names
|
||||
So that I can prevent unwanted file names existing in the cloud storage
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-54
|
||||
Scenario Outline: upload a file to a banned filename
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads file with content "uploaded content" to "blacklisted-file.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" file "blacklisted-file.txt" should not exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-54
|
||||
Scenario Outline: upload a file to a filename that matches (or not) blacklisted_files_regex
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" uploads to these filenames with content "uploaded content" using the webDAV API then the results should be as listed
|
||||
| filename | http-code | exists |
|
||||
| .ext | 403 | no |
|
||||
| filename.ext | 403 | no |
|
||||
| bannedfilename.txt | 403 | no |
|
||||
| containsbannedstring | 403 | no |
|
||||
| this-ContainsBannedString.txt | 403 | no |
|
||||
| /FOLDER/.ext | 403 | no |
|
||||
| /FOLDER/filename.ext | 403 | no |
|
||||
| /FOLDER/bannedfilename.txt | 403 | no |
|
||||
| /FOLDER/containsbannedstring | 403 | no |
|
||||
| /FOLDER/this-ContainsBannedString.txt | 403 | no |
|
||||
| .extension | 201 | yes |
|
||||
| filename.txt | 201 | yes |
|
||||
| bannedfilename | 201 | yes |
|
||||
| bannedfilenamewithoutdot | 201 | yes |
|
||||
| not-contains-banned-string.txt | 201 | yes |
|
||||
| /FOLDER/.extension | 201 | yes |
|
||||
| /FOLDER/filename.txt | 201 | yes |
|
||||
| /FOLDER/bannedfilename | 201 | yes |
|
||||
| /FOLDER/bannedfilenamewithoutdot | 201 | yes |
|
||||
| /FOLDER/not-contains-banned-string.txt | 201 | yes |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
@@ -1,81 +0,0 @@
|
||||
@api
|
||||
Feature: users cannot upload a file to or into an excluded directory
|
||||
As an administrator
|
||||
I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused.
|
||||
So that I can have directories on my cloud server storage that are not available for syncing.
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-54
|
||||
Scenario Outline: upload a file to an excluded directory name
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads file with content "uploaded content" to ".github" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" file ".github" should not exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-54
|
||||
Scenario Outline: upload a file to an excluded directory name inside a parent directory
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" uploads file with content "uploaded content" to "/FOLDER/.github" using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" folder "/FOLDER" should exist
|
||||
But as "Alice" file "/FOLDER/.github" should not exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
|
||||
@issue-ocis-reva-54
|
||||
Scenario Outline: upload a file to a filename that matches (or not) excluded_directories_regex
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" uploads to these filenames with content "uploaded content" using the webDAV API then the results should be as listed
|
||||
| filename | http-code | exists |
|
||||
| endswith.bad | 403 | no |
|
||||
| thisendswith.bad | 403 | no |
|
||||
| .git | 403 | no |
|
||||
| .github | 403 | no |
|
||||
| containsvirusinthename | 403 | no |
|
||||
| this-containsvirusinthename.txt | 403 | no |
|
||||
| /FOLDER/endswith.bad | 403 | no |
|
||||
| /FOLDER/thisendswith.bad | 403 | no |
|
||||
| /FOLDER/.git | 403 | no |
|
||||
| /FOLDER/.github | 403 | no |
|
||||
| /FOLDER/containsvirusinthename | 403 | no |
|
||||
| /FOLDER/this-containsvirusinthename.txt | 403 | no |
|
||||
| endswith.badandotherstuff | 201 | yes |
|
||||
| thisendswith.badandotherstuff | 201 | yes |
|
||||
| name.git | 201 | yes |
|
||||
| name.github | 201 | yes |
|
||||
| not-contains-virus-in-the-name.txt | 201 | yes |
|
||||
| /FOLDER/endswith.badandotherstuff | 201 | yes |
|
||||
| /FOLDER/thisendswith.badandotherstuff | 201 | yes |
|
||||
| /FOLDER/name.git | 201 | yes |
|
||||
| /FOLDER/name.github | 201 | yes |
|
||||
| /FOLDER/not-contains-virus-in-the-name.txt | 201 | yes |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcV10 @personalSpace
|
||||
Examples:
|
||||
| dav_version |
|
||||
| spaces |
|
||||
@@ -1,33 +0,0 @@
|
||||
@api @issue-ocis-reva-15
|
||||
Feature: users cannot upload a file to a blacklisted name using old chunking
|
||||
As an administrator
|
||||
I want to be able to prevent users from uploading files to specified file names
|
||||
So that I can prevent unwanted file names existing in the cloud storage
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And using old DAV path
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
|
||||
Scenario: Upload a file to a banned filename using old chunking
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "blacklisted-file.txt" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" file "blacklisted-file.txt" should not exist
|
||||
|
||||
|
||||
Scenario Outline: upload a file to a filename that matches blacklisted_files_regex using old chunking
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "<filename>" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "<http-status>"
|
||||
And as "Alice" file "<filename>" should not exist
|
||||
Examples:
|
||||
| filename | http-status |
|
||||
| filename.ext | 403 |
|
||||
| bannedfilename.txt | 403 |
|
||||
| this-ContainsBannedString.txt | 403 |
|
||||
|
||||
|
||||
Scenario: upload a file to a filename that does not match blacklisted_files_regex using old chunking
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "not-contains-banned-string.txt" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "not-contains-banned-string.txt" should exist
|
||||
@@ -1,41 +0,0 @@
|
||||
@api @issue-ocis-reva-15
|
||||
Feature: users cannot upload a file to or into an excluded directory using old chunking
|
||||
As an administrator
|
||||
I want to be able to exclude directories (folders) from being processed. Any attempt to upload a file to one of those names should be refused.
|
||||
So that I can have directories on my cloud server storage that are not available for syncing.
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And using old DAV path
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
|
||||
Scenario: Upload a file to an excluded directory name using old chunking
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "/.github" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" file ".github" should not exist
|
||||
|
||||
|
||||
Scenario: Upload a file to an excluded directory name inside a parent directory using old chunking
|
||||
Given user "Alice" has created folder "FOLDER"
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "/FOLDER/.github" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "403"
|
||||
And as "Alice" folder "/FOLDER" should exist
|
||||
But as "Alice" file "/FOLDER/.github" should not exist
|
||||
|
||||
|
||||
Scenario Outline: upload a file to a filename that matches excluded_directories_regex using old chunking
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "<filename>" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "<http-status>"
|
||||
And as "Alice" file "<filename>" should not exist
|
||||
Examples:
|
||||
| filename | http-status |
|
||||
| thisendswith.bad | 503 |
|
||||
| .github | 403 |
|
||||
| this-containsvirusinthename.txt | 403 |
|
||||
|
||||
|
||||
Scenario: upload a file to a filename that does not match excluded_directories_regex using old chunking
|
||||
When user "Alice" uploads file "filesForUpload/textfile.txt" to "not-contains-virus-in-the-name.txt" in 3 chunks using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "not-contains-virus-in-the-name.txt" should exist
|
||||
Reference in New Issue
Block a user