mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-01-26 06:50:36 -05:00
Merge pull request #684 from owncloud/deleteTestsInStorage
[tests-only] delete obsolete API tests from storage
This commit is contained in:
Phil Davis
@@ -1,18 +0,0 @@
|
||||
{
|
||||
"name": "owncloud/ocis-reva",
|
||||
"config" : {
|
||||
"platform": {
|
||||
"php": "7.2"
|
||||
}
|
||||
},
|
||||
"require": {
|
||||
},
|
||||
"require-dev": {
|
||||
"bamarni/composer-bin-plugin": "^1.4"
|
||||
},
|
||||
"extra": {
|
||||
"bamarni-bin": {
|
||||
"bin-links": false
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -1,37 +0,0 @@
|
||||
default:
|
||||
autoload:
|
||||
'': '%paths.base%/../features/bootstrap'
|
||||
|
||||
suites:
|
||||
apiOcisSpecific:
|
||||
paths:
|
||||
- '%paths.base%/../features/apiOcisSpecific'
|
||||
context: &common_ldap_suite_context
|
||||
parameters:
|
||||
ldapAdminPassword: admin
|
||||
ldapUsersOU: TestUsers
|
||||
ldapGroupsOU: TestGroups
|
||||
ldapInitialUserFilePath: /../../config/ldap-users.ldif
|
||||
contexts:
|
||||
- RevaContext:
|
||||
- OccContext:
|
||||
- FeatureContext: &common_feature_context_params
|
||||
baseUrl: http://localhost:8080
|
||||
adminUsername: admin
|
||||
adminPassword: admin
|
||||
regularUserPassword: 123456
|
||||
ocPath: apps/testing/api/v1/occ
|
||||
- CapabilitiesContext:
|
||||
- ChecksumContext:
|
||||
- FavoritesContext:
|
||||
- FilesVersionsContext:
|
||||
- PublicWebDavContext:
|
||||
- TrashbinContext:
|
||||
- WebDavPropertiesContext:
|
||||
|
||||
extensions:
|
||||
jarnaiz\JUnitFormatter\JUnitFormatterExtension:
|
||||
filename: report.xml
|
||||
outputDir: '%paths.base%/../output/'
|
||||
|
||||
Cjm\Behat\StepThroughExtension: ~
|
||||
@@ -1,918 +0,0 @@
|
||||
# this file contains the scenarios from ownCloud10 core API tests that are currently expected to fail
|
||||
# when run with EOS storage
|
||||
#
|
||||
# ToDo: enable testing with EOS in CI and adjust this list to match what actually fails
|
||||
#
|
||||
# test scenarios that fail with OC storage (that were tagged skipOnOcis-OC-Storage in core)
|
||||
#
|
||||
apiShareManagementBasic/createShare.feature:336
|
||||
apiShareManagementBasic/createShare.feature:357
|
||||
apiShareManagementBasic/createShare.feature:478
|
||||
apiShareManagementBasic/createShare.feature:493
|
||||
apiShareManagementBasic/createShare.feature:508
|
||||
apiShareOperations/gettingShares.feature:155
|
||||
apiShareOperations/gettingShares.feature:156
|
||||
apiSharePublicLink2/multilinkSharing.feature:181
|
||||
apiWebdavProperties1/setFileProperties.feature:32
|
||||
apiWebdavProperties1/setFileProperties.feature:33
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/196 Checksum feature
|
||||
apiMain/checksums.feature:24
|
||||
apiMain/checksums.feature:25
|
||||
apiMain/checksums.feature:35
|
||||
apiMain/checksums.feature:36
|
||||
apiMain/checksums.feature:46
|
||||
apiMain/checksums.feature:47
|
||||
apiMain/checksums.feature:50
|
||||
apiMain/checksums.feature:58
|
||||
apiMain/checksums.feature:67
|
||||
apiMain/checksums.feature:99
|
||||
apiMain/checksums.feature:100
|
||||
apiMain/checksums.feature:103
|
||||
apiMain/checksums.feature:110
|
||||
apiMain/checksums.feature:119
|
||||
apiMain/checksums.feature:129
|
||||
apiMain/checksums.feature:138
|
||||
apiMain/checksums.feature:147
|
||||
apiMain/checksums.feature:158
|
||||
apiMain/checksums.feature:174
|
||||
apiMain/checksums.feature:192
|
||||
apiMain/checksums.feature:217
|
||||
apiMain/checksums.feature:218
|
||||
apiMain/checksums.feature:239
|
||||
apiMain/checksums.feature:240
|
||||
apiMain/checksums.feature:258
|
||||
apiMain/checksums.feature:279
|
||||
apiMain/checksums.feature:280
|
||||
apiMain/checksums.feature:295
|
||||
apiMain/checksums.feature:296
|
||||
apiMain/checksums.feature:308
|
||||
apiMain/checksums.feature:309
|
||||
apiMain/checksums.feature:312
|
||||
apiMain/checksums.feature:324
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/100 no robots.txt available
|
||||
apiMain/main.feature:5
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/101 quota query
|
||||
apiMain/quota.feature:9
|
||||
apiMain/quota.feature:16
|
||||
apiMain/quota.feature:23
|
||||
apiMain/quota.feature:30
|
||||
apiMain/quota.feature:41
|
||||
apiMain/quota.feature:54
|
||||
apiMain/quota.feature:68
|
||||
apiMain/quota.feature:82
|
||||
apiMain/quota.feature:99
|
||||
apiMain/quota.feature:112
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/65 There is no such thing like a "super-user"
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/97 no command equivalent to occ
|
||||
apiMain/status.feature:5
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/29 ocs config endpoint only accessible by authorized users
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/30 HTTP 401 Unauthorized responses don't contain a body
|
||||
apiAuthOcs/ocsDELETEAuth.feature:9
|
||||
apiAuthOcs/ocsGETAuth.feature:10
|
||||
apiAuthOcs/ocsGETAuth.feature:33
|
||||
apiAuthOcs/ocsGETAuth.feature:53
|
||||
apiAuthOcs/ocsGETAuth.feature:88
|
||||
apiAuthOcs/ocsGETAuth.feature:121
|
||||
apiAuthOcs/ocsGETAuth.feature:139
|
||||
apiAuthOcs/ocsPOSTAuth.feature:10
|
||||
apiAuthOcs/ocsPUTAuth.feature:10
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/13 server returns 500 when trying to access a not existing file
|
||||
apiAuthWebDav/webDavDELETEAuth.feature:36
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/9 users can access each-others data using the new webdav API
|
||||
apiAuthWebDav/webDavLOCKAuth.feature:38
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/9 users can access each-others data using the new webdav API
|
||||
apiAuthWebDav/webDavMKCOLAuth.feature:37
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiAuthWebDav/webDavMOVEAuth.feature:37
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/179 send POST requests to another user's webDav endpoints as normal user
|
||||
apiAuthWebDav/webDavPOSTAuth.feature:38
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/9 users can access each-others data using the new webdav API
|
||||
apiAuthWebDav/webDavPROPFINDAuth.feature:37
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/9 users can access each-others data using the new webdav API
|
||||
apiAuthWebDav/webDavPROPPATCHAuth.feature:38
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/9 users can access each-others data using the new webdav API
|
||||
apiAuthWebDav/webDavPUTAuth.feature:38
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/175 Default capabilities for normal user not same as in oC-core
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/176 Difference in response content of status.php and default capabilities
|
||||
apiCapabilities/capabilitiesWithNormalUser.feature:11
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/39 REPORT request not implemented
|
||||
apiFavorites/favorites.feature:228
|
||||
apiFavorites/favorites.feature:229
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/34 groups endpoint does not exist
|
||||
apiSharees/sharees.feature:32
|
||||
apiSharees/sharees.feature:33
|
||||
apiSharees/sharees.feature:53
|
||||
apiSharees/sharees.feature:54
|
||||
apiSharees/sharees.feature:74
|
||||
apiSharees/sharees.feature:75
|
||||
apiSharees/sharees.feature:98
|
||||
apiSharees/sharees.feature:99
|
||||
apiSharees/sharees.feature:118
|
||||
apiSharees/sharees.feature:119
|
||||
apiSharees/sharees.feature:137
|
||||
apiSharees/sharees.feature:138
|
||||
apiSharees/sharees.feature:157
|
||||
apiSharees/sharees.feature:158
|
||||
apiSharees/sharees.feature:177
|
||||
apiSharees/sharees.feature:178
|
||||
apiSharees/sharees.feature:198
|
||||
apiSharees/sharees.feature:199
|
||||
apiSharees/sharees.feature:217
|
||||
apiSharees/sharees.feature:218
|
||||
apiSharees/sharees.feature:237
|
||||
apiSharees/sharees.feature:238
|
||||
apiSharees/sharees.feature:257
|
||||
apiSharees/sharees.feature:258
|
||||
apiSharees/sharees.feature:277
|
||||
apiSharees/sharees.feature:278
|
||||
apiSharees/sharees.feature:297
|
||||
apiSharees/sharees.feature:298
|
||||
apiSharees/sharees.feature:317
|
||||
apiSharees/sharees.feature:318
|
||||
apiSharees/sharees.feature:336
|
||||
apiSharees/sharees.feature:337
|
||||
apiSharees/sharees.feature:355
|
||||
apiSharees/sharees.feature:356
|
||||
apiSharees/sharees.feature:374
|
||||
apiSharees/sharees.feature:375
|
||||
apiSharees/sharees.feature:393
|
||||
apiSharees/sharees.feature:394
|
||||
apiSharees/sharees.feature:412
|
||||
apiSharees/sharees.feature:413
|
||||
apiSharees/sharees.feature:430
|
||||
apiSharees/sharees.feature:431
|
||||
apiSharees/sharees.feature:450
|
||||
apiSharees/sharees.feature:451
|
||||
apiSharees/sharees.feature:475
|
||||
apiSharees/sharees.feature:476
|
||||
apiSharees/sharees.feature:495
|
||||
apiSharees/sharees.feature:496
|
||||
apiSharees/sharees.feature:515
|
||||
apiSharees/sharees.feature:516
|
||||
apiSharees/sharees.feature:537
|
||||
apiSharees/sharees.feature:538
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/34 groups endpoint does not exist
|
||||
apiShareManagementBasic/createShare.feature:169
|
||||
apiShareManagementBasic/createShare.feature:170
|
||||
apiShareManagementBasic/createShare.feature:194
|
||||
apiShareManagementBasic/createShare.feature:195
|
||||
apiShareManagementBasic/createShare.feature:417
|
||||
apiShareManagementBasic/createShare.feature:418
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/243 Sharing seems to work but does not work
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/372 Listing shares via ocs API does not show path for parent folders
|
||||
apiShareManagementBasic/createShare.feature:269
|
||||
apiShareManagementBasic/createShare.feature:270
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/356 Fields missing in delete share OCS response
|
||||
apiShareManagementBasic/deleteShare.feature:36
|
||||
apiShareManagementBasic/deleteShare.feature:37
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/260 Sharee retrieves the information about a share -but gets response containing all the shares
|
||||
apiShareOperations/accessToShare.feature:48
|
||||
apiShareOperations/accessToShare.feature:49
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/34 groups endpoint does not exist
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/194 Group shares support
|
||||
apiShareOperations/accessToShare.feature:63
|
||||
apiShareOperations/accessToShare.feature:64
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/262 Shares are not deleted when user is deleted
|
||||
apiShareOperations/gettingShares.feature:21
|
||||
apiShareOperations/gettingShares.feature:22
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/65 There is no such thing like a "super-user"
|
||||
apiShareOperations/gettingShares.feature:34
|
||||
apiShareOperations/gettingShares.feature:35
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/357 Delete shares from user when user is deleted
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/301 no displayname_owner shown when creating a share
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/302 when sharing a file mime-type field is set to application/octet-stream
|
||||
apiShareOperations/gettingShares.feature:124
|
||||
apiShareOperations/gettingShares.feature:125
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/374 OCS error message for attempting to access share via share id as an unauthorized user is not informative
|
||||
apiShareOperations/gettingShares.feature:168
|
||||
apiShareOperations/gettingShares.feature:169
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/194 Group shares support
|
||||
apiShareOperations/gettingShares.feature:172
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/372 Listing shares via ocs API does not show path for parent folders
|
||||
apiShareOperations/gettingShares.feature:204
|
||||
apiShareOperations/gettingShares.feature:205
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/47 cannot get ocs:share-permissions via WebDAV
|
||||
apiShareOperations/getWebDAVSharePermissions.feature:21
|
||||
apiShareOperations/getWebDAVSharePermissions.feature:22
|
||||
apiShareOperations/getWebDAVSharePermissions.feature:134
|
||||
apiShareOperations/getWebDAVSharePermissions.feature:135
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/282 Split old public API webdav tests from new public webdav tests
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/292 Public link enforce permissions
|
||||
apiSharePublicLink1/accessToPublicLinkShare.feature:10
|
||||
apiSharePublicLink1/accessToPublicLinkShare.feature:20
|
||||
apiSharePublicLink1/accessToPublicLinkShare.feature:30
|
||||
apiSharePublicLink1/accessToPublicLinkShare.feature:43
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:22
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:23
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:37
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:41
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:52
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:63
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:85
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:96
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:107
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:151
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:197
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:244
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:267
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:278
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:289
|
||||
apiSharePublicLink1/changingPublicLinkShare.feature:300
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:34
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:35
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/12 Range Header is not obeyed when downloading a file
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:63
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:64
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:95
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:96
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/199 Ability to return error messages in Webdav response bodies
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:127
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:128
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:155
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:156
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/292 Public link enforce permissions
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:183
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:184
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:214
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:215
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/12 Range Header is not obeyed when downloading a file
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:245
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:246
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:276
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:277
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/292 Public link enforce permissions
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:307
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:308
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:370
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:371
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:389
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:390
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:411
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:413
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:435
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:437
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:461
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:463
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:487
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:489
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:491
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:493
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:495
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:497
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:518
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:519
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:534
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:535
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:553
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:554
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:590
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:591
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/283 Prevent creating public share for the home root folder
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:620
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:621
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:634
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:635
|
||||
#
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:663
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:664
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:714
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:715
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/199 Ability to return error messages in Webdav response bodies
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:718
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/292 Public link enforce permissions
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:727
|
||||
#
|
||||
# https://github.com/owncloud/core/issues/37605 Public cannot upload file with mtime set on a public link share with new version of WebDAV API
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:779
|
||||
#
|
||||
# https://github.com/owncloud/core/issues/37605 Public cannot upload file with mtime set on a public link share with new version of WebDAV API
|
||||
apiSharePublicLink1/createPublicLinkShare.feature:793
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/311 Deleting a public link after renaming a file
|
||||
apiSharePublicLink1/deletePublicLinkShare.feature:37
|
||||
apiSharePublicLink1/deletePublicLinkShare.feature:38
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/373 copying a folder within a public link folder to folder with same name as an already existing file overwrites the parent file
|
||||
apiSharePublicLink2/copyFromPublicLink.feature:60
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/368 copying a file from within a public link folder to "/" overwrites the parent folder
|
||||
apiSharePublicLink2/copyFromPublicLink.feature:167
|
||||
apiSharePublicLink2/copyFromPublicLink.feature:168
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/368 copying a file from within a public link folder to "/" overwrites the parent folder
|
||||
apiSharePublicLink2/copyFromPublicLink.feature:183
|
||||
apiSharePublicLink2/copyFromPublicLink.feature:184
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:94
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:95
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:285
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:286
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:304
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:305
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:323
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:324
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:342
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:343
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:361
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:362
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:380
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:381
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:399
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:400
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:418
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:419
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:440
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:441
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/292 Public link enforce permissions
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:462
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:463
|
||||
#
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:487
|
||||
apiSharePublicLink2/updatePublicLinkShare.feature:488
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:9
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/286 Upload-only shares must not overwrite but create a separate file
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:23
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:48
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:49
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/290 Accessing non-existing public link should return 404, not 500
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:62
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:63
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/290 Accessing non-existing public link should return 404, not 500
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:66
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/292 Public link enforce permissions
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:74
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:83
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:103
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:121
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:139
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/195 Set quota over settings
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:148
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:158
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/195 Set quota over settings
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:167
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:177
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:186
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:196
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:206
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:217
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/41 various sharing settings cannot be set
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:227
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:238
|
||||
#
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:255
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/286 Upload-only shares must not overwrite but create a separate file
|
||||
apiSharePublicLink2/uploadToPublicLinkShare.feature:273
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/17 uploading with old-chunking does not work
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiVersions/fileVersions.feature:15
|
||||
apiVersions/fileVersions.feature:23
|
||||
apiVersions/fileVersions.feature:36
|
||||
apiVersions/fileVersions.feature:45
|
||||
apiVersions/fileVersions.feature:88
|
||||
apiVersions/fileVersions.feature:89
|
||||
apiVersions/fileVersions.feature:93
|
||||
apiVersions/fileVersions.feature:104
|
||||
apiVersions/fileVersions.feature:288
|
||||
apiVersions/fileVersions.feature:362
|
||||
apiVersions/fileVersions.feature:373
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove1/moveFileAsync.feature:26
|
||||
apiWebdavMove1/moveFileAsync.feature:27
|
||||
apiWebdavMove1/moveFileAsync.feature:28
|
||||
apiWebdavMove1/moveFileAsync.feature:29
|
||||
apiWebdavMove1/moveFileAsync.feature:30
|
||||
apiWebdavMove1/moveFileAsync.feature:31
|
||||
apiWebdavMove1/moveFileAsync.feature:33
|
||||
apiWebdavMove1/moveFileAsync.feature:46
|
||||
apiWebdavMove1/moveFileAsync.feature:59
|
||||
apiWebdavMove1/moveFileAsync.feature:73
|
||||
apiWebdavMove1/moveFileAsync.feature:88
|
||||
apiWebdavMove1/moveFileAsync.feature:107
|
||||
apiWebdavMove1/moveFileAsync.feature:125
|
||||
apiWebdavMove1/moveFileAsync.feature:135
|
||||
apiWebdavMove1/moveFileAsync.feature:141
|
||||
apiWebdavMove1/moveFileAsync.feature:156
|
||||
apiWebdavMove1/moveFileAsync.feature:173
|
||||
apiWebdavMove1/moveFileAsync.feature:174
|
||||
apiWebdavMove1/moveFileAsync.feature:184
|
||||
apiWebdavMove1/moveFileAsync.feature:185
|
||||
apiWebdavMove1/moveFileAsync.feature:204
|
||||
apiWebdavMove1/moveFileAsync.feature:205
|
||||
apiWebdavMove1/moveFileAsync.feature:224
|
||||
apiWebdavMove1/moveFileAsync.feature:225
|
||||
apiWebdavMove1/moveFileAsync.feature:234
|
||||
apiWebdavMove1/moveFileAsync.feature:235
|
||||
apiWebdavMove1/moveFileAsync.feature:240
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove1/moveFileToBlacklistedNameAsync.feature:12
|
||||
apiWebdavMove1/moveFileToBlacklistedNameAsync.feature:18
|
||||
apiWebdavMove1/moveFileToBlacklistedNameAsync.feature:26
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature:12
|
||||
apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature:19
|
||||
apiWebdavMove1/moveFileToExcludedDirectoryAsync.feature:27
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove1/moveFolder.feature:21
|
||||
apiWebdavMove1/moveFolder.feature:22
|
||||
apiWebdavMove1/moveFolder.feature:34
|
||||
apiWebdavMove1/moveFolder.feature:35
|
||||
apiWebdavMove1/moveFolder.feature:47
|
||||
apiWebdavMove1/moveFolder.feature:48
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove1/moveFolderToBlacklistedName.feature:21
|
||||
apiWebdavMove1/moveFolderToBlacklistedName.feature:22
|
||||
apiWebdavMove1/moveFolderToBlacklistedName.feature:35
|
||||
apiWebdavMove1/moveFolderToBlacklistedName.feature:36
|
||||
apiWebdavMove1/moveFolderToBlacklistedName.feature:70
|
||||
apiWebdavMove1/moveFolderToBlacklistedName.feature:71
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove1/moveFolderToExcludedDirectory.feature:21
|
||||
apiWebdavMove1/moveFolderToExcludedDirectory.feature:22
|
||||
apiWebdavMove1/moveFolderToExcludedDirectory.feature:34
|
||||
apiWebdavMove1/moveFolderToExcludedDirectory.feature:35
|
||||
apiWebdavMove1/moveFolderToExcludedDirectory.feature:70
|
||||
apiWebdavMove1/moveFolderToExcludedDirectory.feature:71
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove2/moveFile.feature:89
|
||||
apiWebdavMove2/moveFile.feature:90
|
||||
apiWebdavMove2/moveFile.feature:91
|
||||
apiWebdavMove2/moveFile.feature:92
|
||||
apiWebdavMove2/moveFile.feature:112
|
||||
apiWebdavMove2/moveFile.feature:113
|
||||
apiWebdavMove2/moveFile.feature:136
|
||||
apiWebdavMove2/moveFile.feature:137
|
||||
apiWebdavMove2/moveFile.feature:138
|
||||
apiWebdavMove2/moveFile.feature:139
|
||||
apiWebdavMove2/moveFile.feature:160
|
||||
apiWebdavMove2/moveFile.feature:161
|
||||
apiWebdavMove2/moveFile.feature:181
|
||||
apiWebdavMove2/moveFile.feature:182
|
||||
apiWebdavMove2/moveFile.feature:200
|
||||
apiWebdavMove2/moveFile.feature:201
|
||||
apiWebdavMove2/moveFile.feature:219
|
||||
apiWebdavMove2/moveFile.feature:220
|
||||
apiWebdavMove2/moveFile.feature:255
|
||||
apiWebdavMove2/moveFile.feature:256
|
||||
apiWebdavMove2/moveFile.feature:272
|
||||
apiWebdavMove2/moveFile.feature:273
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove2/moveFileToBlacklistedName.feature:18
|
||||
apiWebdavMove2/moveFileToBlacklistedName.feature:19
|
||||
apiWebdavMove2/moveFileToBlacklistedName.feature:29
|
||||
apiWebdavMove2/moveFileToBlacklistedName.feature:30
|
||||
apiWebdavMove2/moveFileToBlacklistedName.feature:62
|
||||
apiWebdavMove2/moveFileToBlacklistedName.feature:63
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/14 renaming a resource does not work
|
||||
apiWebdavMove2/moveFileToExcludedDirectory.feature:18
|
||||
apiWebdavMove2/moveFileToExcludedDirectory.feature:19
|
||||
apiWebdavMove2/moveFileToExcludedDirectory.feature:28
|
||||
apiWebdavMove2/moveFileToExcludedDirectory.feature:29
|
||||
apiWebdavMove2/moveFileToExcludedDirectory.feature:63
|
||||
apiWebdavMove2/moveFileToExcludedDirectory.feature:64
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavOperations/deleteFolder.feature:67
|
||||
apiWebdavOperations/deleteFolder.feature:68
|
||||
apiWebdavOperations/deleteFolder.feature:69
|
||||
apiWebdavOperations/deleteFolder.feature:70
|
||||
apiWebdavOperations/deleteFolder.feature:91
|
||||
apiWebdavOperations/deleteFolder.feature:92
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/12 Range Header is not obeyed when downloading a file
|
||||
apiWebdavOperations/downloadFile.feature:29
|
||||
apiWebdavOperations/downloadFile.feature:30
|
||||
#
|
||||
apiWebdavOperations/downloadFile.feature:72
|
||||
apiWebdavOperations/downloadFile.feature:73
|
||||
#
|
||||
apiWebdavOperations/downloadFile.feature:84
|
||||
apiWebdavOperations/downloadFile.feature:85
|
||||
#
|
||||
apiWebdavOperations/refuseAccess.feature:21
|
||||
apiWebdavOperations/refuseAccess.feature:22
|
||||
#
|
||||
apiWebdavOperations/refuseAccess.feature:33
|
||||
apiWebdavOperations/refuseAccess.feature:34
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/39 REPORT request not implemented
|
||||
apiWebdavOperations/search.feature:42
|
||||
apiWebdavOperations/search.feature:43
|
||||
apiWebdavOperations/search.feature:57
|
||||
apiWebdavOperations/search.feature:58
|
||||
apiWebdavOperations/search.feature:74
|
||||
apiWebdavOperations/search.feature:75
|
||||
apiWebdavOperations/search.feature:83
|
||||
apiWebdavOperations/search.feature:84
|
||||
apiWebdavOperations/search.feature:101
|
||||
apiWebdavOperations/search.feature:102
|
||||
apiWebdavOperations/search.feature:119
|
||||
apiWebdavOperations/search.feature:120
|
||||
apiWebdavOperations/search.feature:138
|
||||
apiWebdavOperations/search.feature:139
|
||||
apiWebdavOperations/search.feature:165
|
||||
apiWebdavOperations/search.feature:166
|
||||
apiWebdavOperations/search.feature:191
|
||||
apiWebdavOperations/search.feature:192
|
||||
apiWebdavOperations/search.feature:210
|
||||
apiWebdavOperations/search.feature:211
|
||||
apiWebdavOperations/search.feature:213
|
||||
apiWebdavOperations/search.feature:229
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavProperties1/copyFile.feature:65
|
||||
apiWebdavProperties1/copyFile.feature:66
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavProperties1/copyFile.feature:85
|
||||
apiWebdavProperties1/copyFile.feature:86
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/15 blacklisted filenames like .htaccess & file.parts can be uploaded
|
||||
apiWebdavProperties1/copyFile.feature:102
|
||||
apiWebdavProperties1/copyFile.feature:103
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:116
|
||||
apiWebdavProperties1/copyFile.feature:117
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:129
|
||||
apiWebdavProperties1/copyFile.feature:130
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:146
|
||||
apiWebdavProperties1/copyFile.feature:147
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:165
|
||||
apiWebdavProperties1/copyFile.feature:166
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:202
|
||||
apiWebdavProperties1/copyFile.feature:203
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:350
|
||||
apiWebdavProperties1/copyFile.feature:351
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:370
|
||||
apiWebdavProperties1/copyFile.feature:371
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:395
|
||||
apiWebdavProperties1/copyFile.feature:396
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:422
|
||||
apiWebdavProperties1/copyFile.feature:423
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:448
|
||||
apiWebdavProperties1/copyFile.feature:449
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/387 Getting information about a folder overwritten by a file gives 500 error instead of 404
|
||||
apiWebdavProperties1/copyFile.feature:474
|
||||
apiWebdavProperties1/copyFile.feature:475
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/15 blacklisted filenames like .htaccess & file.parts can be uploaded
|
||||
apiWebdavProperties1/createFolder.feature:71
|
||||
apiWebdavProperties1/createFolder.feature:72
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/168 creating a folder that already exists returns an empty body
|
||||
apiWebdavProperties1/createFolder.feature:85
|
||||
apiWebdavProperties1/createFolder.feature:86
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/168 creating a folder that already exists returns an empty body
|
||||
apiWebdavProperties1/createFolder.feature:99
|
||||
apiWebdavProperties1/createFolder.feature:100
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/101 quota query
|
||||
apiWebdavProperties1/getQuota.feature:17
|
||||
apiWebdavProperties1/getQuota.feature:18
|
||||
apiWebdavProperties1/getQuota.feature:27
|
||||
apiWebdavProperties1/getQuota.feature:28
|
||||
apiWebdavProperties1/getQuota.feature:48
|
||||
apiWebdavProperties1/getQuota.feature:49
|
||||
apiWebdavProperties1/getQuota.feature:61
|
||||
apiWebdavProperties1/getQuota.feature:62
|
||||
apiWebdavProperties1/getQuota.feature:77
|
||||
apiWebdavProperties1/getQuota.feature:78
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties1/setFileProperties.feature:63
|
||||
apiWebdavProperties1/setFileProperties.feature:64
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/214 XML properties in webdav response not properly encoded
|
||||
apiWebdavProperties2/getFileProperties.feature:37
|
||||
apiWebdavProperties2/getFileProperties.feature:39
|
||||
apiWebdavProperties2/getFileProperties.feature:40
|
||||
apiWebdavProperties2/getFileProperties.feature:41
|
||||
apiWebdavProperties2/getFileProperties.feature:43
|
||||
apiWebdavProperties2/getFileProperties.feature:44
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/214 XML properties in webdav response not properly encoded
|
||||
apiWebdavProperties2/getFileProperties.feature:59
|
||||
apiWebdavProperties2/getFileProperties.feature:60
|
||||
apiWebdavProperties2/getFileProperties.feature:61
|
||||
apiWebdavProperties2/getFileProperties.feature:63
|
||||
apiWebdavProperties2/getFileProperties.feature:64
|
||||
apiWebdavProperties2/getFileProperties.feature:66
|
||||
apiWebdavProperties2/getFileProperties.feature:67
|
||||
apiWebdavProperties2/getFileProperties.feature:68
|
||||
apiWebdavProperties2/getFileProperties.feature:70
|
||||
apiWebdavProperties2/getFileProperties.feature:71
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavProperties2/getFileProperties.feature:135
|
||||
apiWebdavProperties2/getFileProperties.feature:136
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavProperties2/getFileProperties.feature:156
|
||||
apiWebdavProperties2/getFileProperties.feature:157
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavProperties2/getFileProperties.feature:174
|
||||
apiWebdavProperties2/getFileProperties.feature:175
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/11 listing received shares does not work
|
||||
apiWebdavProperties2/getFileProperties.feature:206
|
||||
apiWebdavProperties2/getFileProperties.feature:207
|
||||
#
|
||||
apiWebdavProperties2/getFileProperties.feature:218
|
||||
apiWebdavProperties2/getFileProperties.feature:219
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/216 Private link support
|
||||
apiWebdavProperties2/getFileProperties.feature:232
|
||||
apiWebdavProperties2/getFileProperties.feature:233
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/163 trying to access a non-existing resource returns an empty body
|
||||
apiWebdavProperties2/getFileProperties.feature:242
|
||||
apiWebdavProperties2/getFileProperties.feature:243
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:246
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:266
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:301
|
||||
apiWebdavProperties2/getFileProperties.feature:302
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:314
|
||||
apiWebdavProperties2/getFileProperties.feature:315
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:327
|
||||
apiWebdavProperties2/getFileProperties.feature:328
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:376
|
||||
apiWebdavProperties2/getFileProperties.feature:377
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:389
|
||||
apiWebdavProperties2/getFileProperties.feature:390
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:402
|
||||
apiWebdavProperties2/getFileProperties.feature:403
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:415
|
||||
apiWebdavProperties2/getFileProperties.feature:416
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:428
|
||||
apiWebdavProperties2/getFileProperties.feature:429
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:441
|
||||
apiWebdavProperties2/getFileProperties.feature:442
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/217 Some failing tests with Webdav custom properties
|
||||
apiWebdavProperties2/getFileProperties.feature:454
|
||||
apiWebdavProperties2/getFileProperties.feature:455
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/15 blacklisted filenames like .htaccess & file.parts can be uploaded
|
||||
apiWebdavUpload1/uploadFile.feature:112
|
||||
apiWebdavUpload1/uploadFile.feature:113
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:14
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:31
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:48
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:65
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:83
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:92
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:106
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:143
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:144
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:146
|
||||
apiWebdavUpload1/uploadFileAsyncUsingNewChunking.feature:159
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/15 blacklisted filenames like .htaccess & file.parts can be uploaded
|
||||
apiWebdavUpload1/uploadFileToBlacklistedName.feature:19
|
||||
apiWebdavUpload1/uploadFileToBlacklistedName.feature:20
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/54 system configuration options missing
|
||||
apiWebdavUpload1/uploadFileToBlacklistedName.feature:31
|
||||
apiWebdavUpload1/uploadFileToBlacklistedName.feature:32
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/54 system configuration options missing
|
||||
apiWebdavUpload1/uploadFileToBlacklistedName.feature:65
|
||||
apiWebdavUpload1/uploadFileToBlacklistedName.feature:66
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature:14
|
||||
apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature:23
|
||||
apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature:47
|
||||
apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature:48
|
||||
apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature:49
|
||||
apiWebdavUpload1/uploadFileToBlacklistedNameAsyncUsingNewChunking.feature:52
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectory.feature:20
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectory.feature:21
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectory.feature:33
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectory.feature:34
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectory.feature:69
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectory.feature:70
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature:14
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature:24
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature:49
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature:50
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature:51
|
||||
apiWebdavUpload1/uploadFileToExcludedDirectoryAsyncUsingNewChunking.feature:54
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature:12
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature:21
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature:45
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature:46
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature:47
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingNewChunking.feature:50
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/15 blacklisted filenames like .htaccess & file.parts can be uploaded
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:13
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:20
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:37
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:38
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:39
|
||||
apiWebdavUpload2/uploadFileToBlacklistedNameUsingOldChunking.feature:42
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature:12
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature:22
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature:47
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature:48
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature:49
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingNewChunking.feature:52
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/15 blacklisted filenames like .htaccess & file.parts can be uploaded
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:13
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:21
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:39
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:40
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:41
|
||||
apiWebdavUpload2/uploadFileToExcludedDirectoryUsingOldChunking.feature:44
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/56 remote.php/dav/uploads endpoint does not exist
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:12
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:29
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:43
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:57
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:79
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:85
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:94
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:98
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:106
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:135
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:136
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:137
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:157
|
||||
apiWebdavUpload2/uploadFileUsingNewChunking.feature:158
|
||||
#
|
||||
# https://github.com/owncloud/ocis/ocis-revaissues/17 uploading with old-chunking does not work
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:13
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:26
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:35
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:44
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:76
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:77
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:97
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:98
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:99
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:100
|
||||
apiWebdavUpload2/uploadFileUsingOldChunking.feature:101
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -1,27 +0,0 @@
|
||||
@api
|
||||
Feature: auth
|
||||
|
||||
@issue-ocis-reva-30 @issue-ocis-reva-65
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
|
||||
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
|
||||
| endpoint |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/pending/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares/pending/123 |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares/123 |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/shares/pending/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares/pending/123 |
|
||||
| /ocs/v1.php/cloud/apps/testing |
|
||||
| /ocs/v2.php/cloud/apps/testing |
|
||||
| /ocs/v1.php/cloud/groups/group1 |
|
||||
| /ocs/v2.php/cloud/groups/group1 |
|
||||
| /ocs/v1.php/cloud/users/%username% |
|
||||
| /ocs/v2.php/cloud/users/%username% |
|
||||
| /ocs/v1.php/cloud/users/%username%/groups |
|
||||
| /ocs/v2.php/cloud/users/%username%/groups |
|
||||
| /ocs/v1.php/cloud/users/%username%/subadmins |
|
||||
| /ocs/v2.php/cloud/users/%username%/subadmins |
|
||||
Then the HTTP status code of responses on all endpoints should be "401"
|
||||
And the OCS status code of responses on all endpoints should be "notset"
|
||||
@@ -1,112 +0,0 @@
|
||||
@api
|
||||
Feature: auth
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and skeleton files
|
||||
|
||||
@issue-ocis-reva-29
|
||||
@issue-ocis-reva-30
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: using OCS anonymously
|
||||
When a user requests these endpoints with "GET" and no authentication
|
||||
| endpoint |
|
||||
| /ocs/v1.php/apps/files_external/api/v1/mounts |
|
||||
| /ocs/v2.php/apps/files_external/api/v1/mounts |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/pending |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares/pending |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/shares |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares |
|
||||
| /ocs/v1.php/cloud/apps |
|
||||
| /ocs/v2.php/cloud/apps |
|
||||
| /ocs/v1.php/cloud/groups |
|
||||
| /ocs/v2.php/cloud/groups |
|
||||
| /ocs/v1.php/cloud/users |
|
||||
| /ocs/v2.php/cloud/users |
|
||||
| /ocs/v1.php/config |
|
||||
| /ocs/v2.php/config |
|
||||
| /ocs/v1.php/privatedata/getattribute |
|
||||
| /ocs/v2.php/privatedata/getattribute |
|
||||
Then the HTTP status code of responses on all endpoints should be "401"
|
||||
And the OCS status code of responses on all endpoints should be "notset"
|
||||
|
||||
@issue-ocis-reva-11
|
||||
@issue-ocis-reva-30
|
||||
@issue-ocis-reva-31
|
||||
@issue-ocis-reva-32
|
||||
@issue-ocis-reva-33
|
||||
@issue-ocis-reva-34
|
||||
@issue-ocis-reva-35
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: using OCS with non-admin basic auth
|
||||
When the user "Alice" requests these endpoints with "GET" with basic auth
|
||||
| endpoint |
|
||||
| /ocs/v1.php/apps/files_external/api/v1/mounts |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/pending |
|
||||
| /ocs/v1.php/privatedata/getattribute |
|
||||
| /ocs/v1.php/cloud/groups |
|
||||
| /ocs/v1.php/cloud/apps |
|
||||
Then the HTTP status code of responses on all endpoints should be "200"
|
||||
And the OCS status code of responses on all endpoints should be "998"
|
||||
When the user "Alice" requests these endpoints with "GET" with basic auth
|
||||
| endpoint |
|
||||
| /ocs/v1.php/config |
|
||||
Then the HTTP status code of responses on all endpoints should be "200"
|
||||
And the OCS status code of responses on all endpoints should be "100"
|
||||
When the user "Alice" requests these endpoints with "GET" with basic auth
|
||||
| endpoint |
|
||||
| /ocs/v2.php/apps/files_external/api/v1/mounts |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares/pending |
|
||||
# | /ocs/v1.php/apps/files_sharing/api/v1/shares | 100 | 200 |
|
||||
# | /ocs/v2.php/apps/files_sharing/api/v1/shares | 100 | 200 |
|
||||
|
||||
| /ocs/v2.php/cloud/apps |
|
||||
| /ocs/v2.php/cloud/groups |
|
||||
| /ocs/v2.php/privatedata/getattribute |
|
||||
Then the HTTP status code of responses on all endpoints should be "404"
|
||||
And the OCS status code of responses on all endpoints should be "998"
|
||||
When the user "Alice" requests these endpoints with "GET" with basic auth
|
||||
| endpoint |
|
||||
| /ocs/v1.php/cloud/users |
|
||||
Then the HTTP status code of responses on all endpoints should be "200"
|
||||
And the OCS status code of responses on all endpoints should be "403"
|
||||
When the user "Alice" requests these endpoints with "GET" with basic auth
|
||||
| endpoint |
|
||||
| /ocs/v2.php/cloud/users |
|
||||
Then the HTTP status code of responses on all endpoints should be "403"
|
||||
And the OCS status code of responses on all endpoints should be "403"
|
||||
When the user "Alice" requests these endpoints with "GET" with basic auth
|
||||
| endpoint |
|
||||
| /ocs/v2.php/config |
|
||||
Then the HTTP status code of responses on all endpoints should be "200"
|
||||
And the OCS status code of responses on all endpoints should be "200"
|
||||
|
||||
@issue-ocis-reva-29
|
||||
@issue-ocis-reva-30
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: using OCS as normal user with wrong password
|
||||
When user "Alice" requests these endpoints with "GET" using password "invalid"
|
||||
| endpoint |
|
||||
| /ocs/v1.php/apps/files_external/api/v1/mounts |
|
||||
| /ocs/v2.php/apps/files_external/api/v1/mounts |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/pending |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares/pending |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/shares |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares |
|
||||
| /ocs/v1.php/cloud/apps |
|
||||
| /ocs/v2.php/cloud/apps |
|
||||
| /ocs/v1.php/cloud/groups |
|
||||
| /ocs/v2.php/cloud/groups |
|
||||
| /ocs/v1.php/cloud/users |
|
||||
| /ocs/v2.php/cloud/users |
|
||||
| /ocs/v1.php/config |
|
||||
| /ocs/v2.php/config |
|
||||
| /ocs/v1.php/privatedata/getattribute |
|
||||
| /ocs/v2.php/privatedata/getattribute |
|
||||
Then the HTTP status code of responses on all endpoints should be "401"
|
||||
And the OCS status code of responses on all endpoints should be "notset"
|
||||
@@ -1,35 +0,0 @@
|
||||
@api
|
||||
Feature: auth
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and skeleton files
|
||||
|
||||
@issue-ocis-reva-30
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: send POST requests to OCS endpoints as normal user with wrong password
|
||||
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
|
||||
| endpoint |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/pending/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/remote_shares/pending/123 |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/shares |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/shares/pending/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares/pending/123 |
|
||||
| /ocs/v1.php/cloud/apps/testing |
|
||||
| /ocs/v2.php/cloud/apps/testing |
|
||||
| /ocs/v1.php/cloud/groups |
|
||||
| /ocs/v2.php/cloud/groups |
|
||||
| /ocs/v1.php/cloud/users |
|
||||
| /ocs/v2.php/cloud/users |
|
||||
| /ocs/v1.php/cloud/users/%username%/groups |
|
||||
| /ocs/v2.php/cloud/users/%username%/groups |
|
||||
| /ocs/v1.php/cloud/users/%username%/subadmins |
|
||||
| /ocs/v2.php/cloud/users/%username%/subadmins |
|
||||
| /ocs/v1.php/person/check |
|
||||
| /ocs/v2.php/person/check |
|
||||
| /ocs/v1.php/privatedata/deleteattribute/testing/test |
|
||||
| /ocs/v2.php/privatedata/deleteattribute/testing/test |
|
||||
| /ocs/v1.php/privatedata/setattribute/testing/test |
|
||||
| /ocs/v2.php/privatedata/setattribute/testing/test |
|
||||
Then the HTTP status code of responses on all endpoints should be "401"
|
||||
And the OCS status code of responses on all endpoints should be "notset"
|
||||
@@ -1,18 +0,0 @@
|
||||
@api
|
||||
Feature: auth
|
||||
|
||||
@issue-ocis-reva-30
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: send PUT request to OCS endpoints as admin with wrong password
|
||||
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
|
||||
| endpoint |
|
||||
| /ocs/v1.php/cloud/users/%username% |
|
||||
| /ocs/v2.php/cloud/users/%username% |
|
||||
| /ocs/v1.php/cloud/users/%username%/disable |
|
||||
| /ocs/v2.php/cloud/users/%username%/disable |
|
||||
| /ocs/v1.php/cloud/users/%username%/enable |
|
||||
| /ocs/v2.php/cloud/users/%username%/enable |
|
||||
| /ocs/v1.php/apps/files_sharing/api/v1/shares/123 |
|
||||
| /ocs/v2.php/apps/files_sharing/api/v1/shares/123 |
|
||||
Then the HTTP status code of responses on all endpoints should be "401"
|
||||
And the OCS status code of responses on all endpoints should be "notset"
|
||||
@@ -1,21 +0,0 @@
|
||||
@api
|
||||
Feature: LOCK file/folder
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-9
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: send LOCK requests to another user's webDav endpoints as normal user
|
||||
When user "Brian" requests these endpoints with "LOCK" to get property "d:shared" about user "Alice"
|
||||
| endpoint |
|
||||
| /remote.php/dav/files/%username%/textfile0.txt |
|
||||
| /remote.php/dav/files/%username%/PARENT |
|
||||
| /remote.php/dav/files/%username%/PARENT/parent.txt |
|
||||
Then the HTTP status code of responses on all endpoints should be "200"
|
||||
@@ -1,20 +0,0 @@
|
||||
@api
|
||||
Feature: MOVE file/folder
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-14
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: send MOVE requests to another user's webDav endpoints as normal user
|
||||
When user "Brian" requests these endpoints with "MOVE" including body "doesnotmatter" about user "Alice"
|
||||
| endpoint |
|
||||
| /remote.php/dav/files/%username%/textfile0.txt |
|
||||
| /remote.php/dav/files/%username%/PARENT |
|
||||
| /remote.php/dav/files/%username%/PARENT/parent.txt |
|
||||
Then the HTTP status code of responses on all endpoints should be "400"
|
||||
@@ -1,20 +0,0 @@
|
||||
@api
|
||||
Feature: get file info using PROPFIND
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-9 @skipOnOcis-EOS-Storage @issue-ocis-reva-303
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: send PROPFIND requests to another user's webDav endpoints as normal user
|
||||
When user "Brian" requests these endpoints with "PROPFIND" to get property "d:getetag" about user "Alice"
|
||||
| endpoint |
|
||||
| /remote.php/dav/files/%username%/textfile0.txt |
|
||||
| /remote.php/dav/files/%username%/PARENT |
|
||||
| /remote.php/dav/files/%username%/PARENT/parent.txt |
|
||||
Then the HTTP status code of responses on all endpoints should be "207"
|
||||
@@ -1,48 +0,0 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: default capabilities for normal user
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-175 @issue-ocis-reva-176
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: getting default capabilities with normal user
|
||||
When user "Alice" retrieves the capabilities using the capabilities API
|
||||
Then the capabilities should contain
|
||||
| capability | path_to_element | value |
|
||||
| core | pollinterval | 60 |
|
||||
| core | webdav-root | remote.php/webdav |
|
||||
| core | status@@@edition | %edition% |
|
||||
| core | status@@@productname | reva |
|
||||
| core | status@@@version | 10.0.11.5 |
|
||||
| core | status@@@versionstring | 10.0.11 |
|
||||
| files_sharing | api_enabled | 1 |
|
||||
| files_sharing | default_permissions | 22 |
|
||||
| files_sharing | search_min_length | 3 |
|
||||
| files_sharing | public@@@enabled | 1 |
|
||||
| files_sharing | public@@@multiple | 1 |
|
||||
| files_sharing | public@@@upload | 1 |
|
||||
| files_sharing | public@@@supports_upload_only | 1 |
|
||||
| files_sharing | public@@@send_mail | 1 |
|
||||
| files_sharing | public@@@social_share | 1 |
|
||||
| files_sharing | public@@@enforced | EMPTY |
|
||||
| files_sharing | public@@@enforced_for@@@read_only | EMPTY |
|
||||
| files_sharing | public@@@enforced_for@@@read_write | EMPTY |
|
||||
| files_sharing | public@@@enforced_for@@@upload_only | EMPTY |
|
||||
| files_sharing | public@@@enforced_for@@@read_write_delete | EMPTY |
|
||||
| files_sharing | public@@@expire_date@@@enabled | 1 |
|
||||
| files_sharing | public@@@defaultPublicLinkShareName | EMPTY |
|
||||
| files_sharing | resharing | 1 |
|
||||
| files_sharing | federation@@@outgoing | 1 |
|
||||
| files_sharing | federation@@@incoming | 1 |
|
||||
| files_sharing | group_sharing | 1 |
|
||||
| files_sharing | share_with_group_members_only | 1 |
|
||||
| files_sharing | share_with_membership_groups_only | 1 |
|
||||
| files_sharing | auto_accept_share | 1 |
|
||||
| files_sharing | user_enumeration@@@enabled | 1 |
|
||||
| files_sharing | user_enumeration@@@group_members_only | 1 |
|
||||
| files_sharing | user@@@send_mail | 1 |
|
||||
| files | bigfilechunking | 0 |
|
||||
| files | privateLinks | 0 |
|
||||
| files | privateLinksDetailsParam | EMPTY |
|
||||
@@ -1,25 +0,0 @@
|
||||
@api
|
||||
Feature: favorite
|
||||
|
||||
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 "some data" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile2.txt"
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile3.txt"
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile4.txt"
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
|
||||
|
||||
@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
|
||||
When user "Alice" favorites element "/FOLDER" using the WebDAV API
|
||||
Then the HTTP status code should be "500"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,57 +0,0 @@
|
||||
@api
|
||||
Feature: checksums
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-98
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Uploading a file with checksum should return the checksum in the download header
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
When user "Alice" downloads file "/myChecksumFile.txt" using the WebDAV API
|
||||
Then the following headers should not be set
|
||||
| header |
|
||||
| OC-Checksum |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-ocis-reva-98
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: Copying file with checksum should return the checksum in the download header using new DAV path
|
||||
Given using new DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
|
||||
When user "Alice" copies file "/myChecksumFile.txt" to "/myChecksumFileCopy.txt" using the WebDAV API
|
||||
And user "Alice" downloads file "/myChecksumFileCopy.txt" using the WebDAV API
|
||||
Then the following headers should not be set
|
||||
| header |
|
||||
| OC-Checksum |
|
||||
|
||||
@issue-ocis-reva-99
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Upload a file where checksum does not match
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads file with checksum "SHA1:f005ba11" and content "Some Text" to "/chksumtst.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And user "Alice" should see the following elements
|
||||
| /chksumtst.txt |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-ocis-reva-99
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Uploaded file should have the same checksum when downloaded
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/chksumtst.txt"
|
||||
When user "Alice" downloads file "/chksumtst.txt" using the WebDAV API
|
||||
Then the following headers should not be set
|
||||
| header |
|
||||
| OC-Checksum |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,8 +0,0 @@
|
||||
@api
|
||||
Feature: Other tests related to api
|
||||
|
||||
@issue-ocis-reva-100
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: robots.txt file should be accessible
|
||||
When a user requests "/robots.txt" with "GET" and no authentication
|
||||
Then the HTTP status code should be "401" or "404"
|
||||
@@ -1,45 +0,0 @@
|
||||
@api @files_sharing-app-required @issue-ocis-reva-243
|
||||
Feature: cannot share resources with invalid permissions
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
|
||||
@issue-ocis-reva-45 @issue-ocis-reva-243
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Cannot create a share of a file with a user with only create permission
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
When user "Alice" creates a share using the sharing API with settings
|
||||
| path | textfile0.txt |
|
||||
| shareWith | Brian |
|
||||
| shareType | user |
|
||||
| permissions | create |
|
||||
Then the OCS status code should be "<ocs_status_code>" or "<eos_status_code>"
|
||||
And the HTTP status code should be "<http_status_code_ocs>" or "<http_status_code_eos>"
|
||||
And as "Brian" entry "textfile0.txt" should not exist
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code | eos_status_code | http_status_code_ocs | http_status_code_eos |
|
||||
| 1 | 100 | 996 | 200 | 500 |
|
||||
| 2 | 200 | 996 | 200 | 500 |
|
||||
|
||||
@issue-ocis-reva-45 @issue-ocis-reva-243
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Cannot create a share of a file with a user with only (create,delete) permission
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
When user "Alice" creates a share using the sharing API with settings
|
||||
| path | textfile0.txt |
|
||||
| shareWith | Brian |
|
||||
| shareType | user |
|
||||
| permissions | <permissions> |
|
||||
Then the OCS status code should be "<ocs_status_code>" or "<eos_status_code>"
|
||||
And the HTTP status code should be "<http_status_code_ocs>" or "<http_status_code_eos>"
|
||||
And as "Brian" entry "textfile0.txt" should not exist
|
||||
Examples:
|
||||
| ocs_api_version | eos_status_code | ocs_status_code | http_status_code_ocs | http_status_code_eos | permissions |
|
||||
| 1 | 100 | 996 | 200 | 500 | delete |
|
||||
| 2 | 200 | 996 | 200 | 500 | delete |
|
||||
| 1 | 100 | 996 | 200 | 500 | create,delete |
|
||||
| 2 | 200 | 996 | 200 | 500 | create,delete |
|
||||
@@ -1,117 +0,0 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: sharing
|
||||
|
||||
Background:
|
||||
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 @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>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
When user "Alice" shares file "textfile0.txt" with user "Brian" with permissions <requested_permissions> using the sharing API
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the HTTP status code should be "200"
|
||||
And the fields of the last response to user "Alice" sharing with user "Brian" should include
|
||||
| share_with | %username% |
|
||||
| file_target | /textfile0.txt |
|
||||
| path | /textfile0.txt |
|
||||
| permissions | <granted_permissions> |
|
||||
| uid_owner | %username% |
|
||||
| displayname_owner | |
|
||||
| item_type | file |
|
||||
| mimetype | application/octet-stream |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the fields of the last response should not include
|
||||
| share_with_displayname | %displayname% |
|
||||
Examples:
|
||||
| ocs_api_version | requested_permissions | granted_permissions | ocs_status_code |
|
||||
# Ask for full permissions. You get share plus read plus update. create and delete do not apply to shares of a file
|
||||
| 1 | 31 | 19 | 100 |
|
||||
| 2 | 31 | 19 | 200 |
|
||||
# Ask for read, share (17), create and delete. You get share plus read
|
||||
| 1 | 29 | 17 | 100 |
|
||||
| 2 | 29 | 17 | 200 |
|
||||
# Ask for read, update, create, delete. You get read plus update.
|
||||
| 1 | 15 | 3 | 100 |
|
||||
| 2 | 15 | 3 | 200 |
|
||||
# Ask for just update. You get exactly update (you do not get read or anything else)
|
||||
| 1 | 2 | 2 | 100 |
|
||||
| 2 | 2 | 2 | 200 |
|
||||
|
||||
@issue-ocis-reva-243
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: more tests to demonstrate different ocis-reva issue 243 behaviours
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/home"
|
||||
And user "Alice" has uploaded file with content "Random data" to "/home/randomfile.txt"
|
||||
When user "Alice" shares file "/home/randomfile.txt" with user "Brian" using the sharing API
|
||||
And the HTTP status code should be "<http_status_code_ocs>" or "<http_status_code_eos>"
|
||||
And as "Brian" file "randomfile.txt" should not exist
|
||||
Examples:
|
||||
| ocs_api_version | http_status_code_ocs | http_status_code_eos |
|
||||
| 1 | 200 | 500 |
|
||||
| 2 | 200 | 500 |
|
||||
|
||||
@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>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/FOLDER"
|
||||
When user "Alice" shares folder "/FOLDER" with user "Brian" using the sharing API
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the HTTP status code should be "200"
|
||||
And the fields of the last response to user "Alice" sharing with user "Brian" should include
|
||||
| share_with | %username% |
|
||||
| file_target | /FOLDER |
|
||||
| path | /FOLDER |
|
||||
| permissions | all |
|
||||
| uid_owner | %username% |
|
||||
| displayname_owner | |
|
||||
| item_type | folder |
|
||||
| mimetype | httpd/unix-directory |
|
||||
| storage_id | ANY_VALUE |
|
||||
| share_type | user |
|
||||
And the fields of the last response should not include
|
||||
| share_with_displayname | %displayname% |
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
|
||||
@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>"
|
||||
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 "/folder1/folder2" should be included as path in the response
|
||||
And folder "/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 "/folder1/folder2" should be included as path in the response
|
||||
And folder "/folder2" should be included as path in the response
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
@@ -1,17 +0,0 @@
|
||||
@api @files_sharing-app-required @issue-ocis-reva-243
|
||||
Feature: sharing
|
||||
|
||||
@issue-ocis-reva-356
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: delete a share
|
||||
Given user "Alice" has been created with default attributes and skeleton files
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And using OCS API version "<ocs_api_version>"
|
||||
And user "Alice" has shared file "textfile0.txt" with user "Brian"
|
||||
When user "Alice" deletes the last share using the sharing API
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the HTTP status code should be "200"
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
@@ -1,23 +0,0 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: sharing
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes and skeleton files:
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
|
||||
@issue-ocis-reva-260
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
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 |
|
||||
@@ -1,23 +0,0 @@
|
||||
@api @files_sharing-app-required @issue-ocis-reva-47
|
||||
Feature: sharing
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And these users have been created with default attributes and without skeleton files:
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
|
||||
@issue-ocis-reva-47
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Empty webdav share-permissions for owned file
|
||||
Given using <dav-path> DAV path
|
||||
And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
|
||||
When user "Alice" gets the following properties of file "/tmp.txt" using the WebDAV API
|
||||
| propertyName |
|
||||
| ocs:share-permissions |
|
||||
Then the single response should contain a property "ocs:share-permissions" with value "5"
|
||||
Examples:
|
||||
| dav-path |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,37 +0,0 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: sharing
|
||||
|
||||
Background:
|
||||
Given these users have been created with default attributes and skeleton files:
|
||||
| username |
|
||||
| Alice |
|
||||
| Brian |
|
||||
|
||||
@issue-ocis-reva-374
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
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 "998"
|
||||
# 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 | 404 |
|
||||
|
||||
@issue-ocis-reva-372
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
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 |
|
||||
@@ -1,31 +0,0 @@
|
||||
@api @files_sharing-app-required @public_link_share-feature-required @skipOnOcis-EOS-Storage @issue-ocis-reva-315 @issue-ocis-reva-316
|
||||
|
||||
Feature: create a public link share
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and skeleton files
|
||||
|
||||
@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"
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | /testFolder |
|
||||
| permissions | read,update,create,delete |
|
||||
When the public uploads file "file.txt" to the last shared folder with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the new public WebDAV API
|
||||
Then as "Alice" file "testFolder/file.txt" should exist
|
||||
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 @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"
|
||||
When user "Alice" uploads file with content "uploaded content for file name ending with a dot" to "testFolder/file.txt" using the WebDAV API
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | /testFolder |
|
||||
| permissions | read,update,create,delete |
|
||||
And the public uploads file "file.txt" to the last shared folder with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the new public WebDAV API
|
||||
Then as "Alice" file "/testFolder/file.txt" should exist
|
||||
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"
|
||||
@@ -1,67 +0,0 @@
|
||||
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-310
|
||||
Feature: copying from public link share
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/PARENT"
|
||||
And the administrator has enabled DAV tech_preview
|
||||
|
||||
@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"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
|
||||
And user "Alice" has uploaded file with content "some data 1" to "/PARENT/copy1.txt"
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | /PARENT |
|
||||
| permissions | read,update,create,delete |
|
||||
When the public copies folder "/testFolder" to "/copy1.txt" using the new public WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" folder "/PARENT/testFolder" should exist
|
||||
And as "Alice" file "/PARENT/copy1.txt" should exist
|
||||
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 @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"
|
||||
And user "Alice" has created folder "/PARENT/new-folder"
|
||||
And user "Alice" has uploaded file with content "some data 1" to "/PARENT/new-folder/testfile1.txt"
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | /PARENT |
|
||||
| permissions | read,update,create,delete |
|
||||
When the public copies file "/testfile.txt" to "/new-folder" using the new public WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" file "/PARENT/testfile.txt" should exist
|
||||
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 @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"
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | /PARENT |
|
||||
| permissions | read,update,create,delete |
|
||||
When the public copies file "/testfile.txt" to "/<destination-file-name>" using the new public WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" file "/PARENT/<destination-file-name>" should exist
|
||||
And the content of file "/PARENT/<destination-file-name>" for user "Alice" should be "some data"
|
||||
Examples:
|
||||
| destination-file-name |
|
||||
| testfile.txt |
|
||||
| |
|
||||
|
||||
@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"
|
||||
And user "Alice" has uploaded file with content "some data" to "/PARENT/testFolder/testfile.txt"
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | /PARENT |
|
||||
| permissions | read,update,create,delete |
|
||||
When the public copies folder "/testFolder" to "/testFolder" using the new public WebDAV API
|
||||
Then the HTTP status code should be "204"
|
||||
And as "Alice" folder "/PARENT/testFolder" should exist
|
||||
And the content of file "/PARENT/testFolder/testfile.txt" for user "Alice" should be "some data"
|
||||
@@ -1,47 +0,0 @@
|
||||
@api @files_sharing-app-required @public_link_share-feature-required @issue-ocis-reva-252
|
||||
Feature: update a public link share
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and skeleton files
|
||||
|
||||
@issue-ocis-reva-243 @issue-ocis-reva-349 @issue-37653
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: API responds with a full set of parameters when owner changes the expireDate of a public share
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
When user "Alice" creates a public link share using the sharing API with settings
|
||||
| path | FOLDER |
|
||||
And user "Alice" updates the last share using the sharing API with
|
||||
| expireDate | +3 days |
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the OCS status message should be "OK"
|
||||
And the HTTP status code should be "200"
|
||||
And the fields of the last response to user "Alice" should include
|
||||
| id | A_STRING |
|
||||
| share_type | public_link |
|
||||
| uid_owner | %username% |
|
||||
| displayname_owner | %displayname% |
|
||||
| permissions | read |
|
||||
| stime | A_NUMBER |
|
||||
| parent | |
|
||||
| expiration | A_STRING |
|
||||
| token | A_STRING |
|
||||
| uid_file_owner | %username% |
|
||||
| displayname_file_owner | %displayname% |
|
||||
| additional_info_owner | |
|
||||
| additional_info_file_owner | |
|
||||
| state | 0 |
|
||||
| item_type | folder |
|
||||
| item_source | A_STRING |
|
||||
| path | /FOLDER |
|
||||
| mimetype | httpd/unix-directory |
|
||||
| storage_id | A_STRING |
|
||||
| storage | A_NUMBER |
|
||||
| file_source | A_STRING |
|
||||
| file_target | /FOLDER |
|
||||
| mail_send | 0 |
|
||||
| name | |
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
@@ -1,17 +0,0 @@
|
||||
@api @files_sharing-app-required @public_link_share-feature-required @skipOnOcis-EOS-Storage @issue-ocis-reva-315 @issue-ocis-reva-316
|
||||
|
||||
Feature: upload to a public link share
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and skeleton files
|
||||
|
||||
@issue-ocis-reva-290
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: Uploading file to a public upload-only share that was deleted does not work
|
||||
Given the administrator has enabled DAV tech_preview
|
||||
And user "Alice" has created a public link share with settings
|
||||
| path | FOLDER |
|
||||
| permissions | create |
|
||||
When user "Alice" deletes file "/FOLDER" using the WebDAV API
|
||||
And the public uploads file "does-not-matter.txt" with content "does not matter" using the new public WebDAV API
|
||||
Then the HTTP status code should be "500"
|
||||
@@ -1,124 +0,0 @@
|
||||
@api @files_sharing-app-required
|
||||
Feature: sharing
|
||||
|
||||
Background:
|
||||
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-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:
|
||||
| username |
|
||||
| Brian |
|
||||
| Carol |
|
||||
And user "Alice" has created folder "/Alice-folder"
|
||||
And user "Alice" has created folder "/Alice-folder/folder2"
|
||||
And user "Carol" has created folder "/Carol-folder"
|
||||
And user "Alice" has shared folder "/Alice-folder" with user "Brian" with permissions "all"
|
||||
And user "Carol" has shared folder "/Carol-folder" with user "Brian" with permissions "all"
|
||||
When user "Brian" moves folder "/Alice-folder/folder2" to "/Carol-folder/folder2" using the WebDAV API
|
||||
And user "Carol" gets the info of the last share using the sharing API
|
||||
# Note: in the following fields, file_parent has been removed because OCIS does not report that
|
||||
Then the fields of the last response to user "Carol" sharing with user "Brian" should include
|
||||
| id | A_STRING |
|
||||
| item_type | folder |
|
||||
| item_source | A_STRING |
|
||||
| share_type | user |
|
||||
| file_source | A_STRING |
|
||||
| file_target | /Carol-folder |
|
||||
| permissions | all |
|
||||
| stime | A_NUMBER |
|
||||
| storage | A_STRING |
|
||||
| mail_send | 0 |
|
||||
| uid_owner | %username% |
|
||||
| displayname_owner | %displayname% |
|
||||
| mimetype | httpd/unix-directory |
|
||||
# Really folder2 should be gone from Alice-folder and be found in Carol-folder
|
||||
# like in these 2 suggested steps:
|
||||
# And as "Alice" folder "/Alice-folder/folder2" should not exist
|
||||
# And as "Carol" folder "/Carol-folder/folder2" should exist
|
||||
#
|
||||
# But this happens on OCIS:
|
||||
And as "Alice" folder "/Alice-folder/folder2" should exist
|
||||
And as "Carol" folder "/Carol-folder/folder2" should not exist
|
||||
|
||||
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @toFixOnOCIS @issue-ocis-reva-243
|
||||
# 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
|
||||
Given these users have been created with default attributes and without skeleton files:
|
||||
| username |
|
||||
| Brian |
|
||||
| Carol |
|
||||
And user "Alice" has created folder "/Alice-folder"
|
||||
And user "Alice" has created folder "/Alice-folder/folder2"
|
||||
And user "Carol" has created folder "/Carol-folder"
|
||||
And user "Alice" has shared folder "/Alice-folder" with user "Brian" with permissions "all"
|
||||
And user "Carol" has shared folder "/Carol-folder" with user "Brian" with permissions "all"
|
||||
When user "Brian" moves folder "/Alice-folder/folder2" to "/Carol-folder/folder2" using the WebDAV API
|
||||
And user "Carol" gets the info of the last share using the sharing API
|
||||
Then the fields of the last response to user "Carol" sharing with user "Brian" should include
|
||||
| id | A_STRING |
|
||||
| item_type | folder |
|
||||
| item_source | A_STRING |
|
||||
| share_type | user |
|
||||
| file_source | A_STRING |
|
||||
| file_target | /Carol-folder |
|
||||
| permissions | all |
|
||||
| stime | A_NUMBER |
|
||||
| storage | A_STRING |
|
||||
| mail_send | 0 |
|
||||
| uid_owner | %username% |
|
||||
| mimetype | httpd/unix-directory |
|
||||
And as "Alice" folder "/Alice-folder/folder2" should exist
|
||||
And as "Carol" folder "/Carol-folder/folder2" should not exist
|
||||
|
||||
@toFixOnOCIS @toFixOnOcV10 @issue-ocis-reva-243 @issue-ocis-reva-349 @issue-ocis-reva-350 @issue-ocis-reva-352 @issue-37653
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: API responds with a full set of parameters when owner changes the permission of a share
|
||||
Given using OCS API version "<ocs_api_version>"
|
||||
And user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has created folder "/Alice-folder"
|
||||
And user "Alice" has shared folder "/Alice-folder" with user "Brian" with permissions "read"
|
||||
When user "Alice" updates the last share using the sharing API with
|
||||
| permissions | all |
|
||||
Then the OCS status code should be "<ocs_status_code>"
|
||||
And the OCS status message should be "OK"
|
||||
And the HTTP status code should be "200"
|
||||
Then the fields of the last response to user "Alice" sharing with user "Brian" should include
|
||||
| id | A_STRING |
|
||||
| share_type | user |
|
||||
| uid_owner | %username% |
|
||||
| displayname_owner | %displayname% |
|
||||
| permissions | all |
|
||||
| stime | A_NUMBER |
|
||||
| parent | |
|
||||
| expiration | |
|
||||
| token | |
|
||||
| uid_file_owner | %username% |
|
||||
| displayname_file_owner | %displayname% |
|
||||
| additional_info_owner | |
|
||||
| additional_info_file_owner | |
|
||||
| state | 0 |
|
||||
| item_type | folder |
|
||||
| item_source | A_STRING |
|
||||
| path | /Alice-folder |
|
||||
| mimetype | httpd/unix-directory |
|
||||
| storage_id | A_STRING |
|
||||
| storage | 0 |
|
||||
| file_source | A_STRING |
|
||||
| file_target | /Alice-folder |
|
||||
| share_with | %username% |
|
||||
| share_with_displayname | %displayname% |
|
||||
| share_with_additional_info | |
|
||||
| mail_send | 0 |
|
||||
| name | |
|
||||
And the fields of the last response should not include
|
||||
| attributes | |
|
||||
# | token | |
|
||||
# | name | |
|
||||
Examples:
|
||||
| ocs_api_version | ocs_status_code |
|
||||
| 1 | 100 |
|
||||
| 2 | 200 |
|
||||
@@ -1,55 +0,0 @@
|
||||
@api @files_trashbin-app-required
|
||||
Feature: files and folders can be deleted from the trashbin
|
||||
As a user
|
||||
I want to delete files and folders from the trashbin
|
||||
So that I can control my trashbin space and which files are kept in that space
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "to delete" to "/textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "to delete" to "/textfile1.txt"
|
||||
And user "Alice" has created folder "PARENT"
|
||||
And user "Alice" has created folder "PARENT/CHILD"
|
||||
And user "Alice" has uploaded file with content "to delete" to "/PARENT/parent.txt"
|
||||
And user "Alice" has uploaded file with content "to delete" to "/PARENT/CHILD/child.txt"
|
||||
|
||||
@smokeTest
|
||||
@issue-product-139
|
||||
@issue-product-178
|
||||
@issue-product-179
|
||||
Scenario Outline: Trashbin cannot be emptied
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
# because of @issue-product-178 we cannot perform this test using new dav, so only old dav is being used
|
||||
Given user "Alice" has uploaded file with content "file with comma" to "sample,0.txt"
|
||||
And user "Alice" has uploaded file with content "file with comma" to "sample,1.txt"
|
||||
And using <dav-path> DAV path
|
||||
And user "Alice" has deleted file "<filename1>"
|
||||
And user "Alice" has deleted file "<filename2>"
|
||||
And as "Alice" file "<filename1>" should exist in the trashbin
|
||||
And as "Alice" file "<filename2>" should exist in the trashbin
|
||||
When user "Alice" empties the trashbin using the trashbin API
|
||||
Then as "Alice" the file with original path "<filename1>" should exist in the trashbin
|
||||
And as "Alice" the file with original path "<filename2>" should exist in the trashbin
|
||||
Examples:
|
||||
| dav-path | filename1 | filename2 |
|
||||
| old | textfile0.txt | textfile1.txt |
|
||||
| old | sample,0.txt | sample,1.txt |
|
||||
| new | textfile0.txt | textfile1.txt |
|
||||
| new | sample,0.txt | sample,1.txt |
|
||||
|
||||
@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"
|
||||
And user "Alice" has deleted file "/textfile1.txt"
|
||||
And user "Alice" has deleted file "/PARENT/parent.txt"
|
||||
And user "Alice" has deleted file "/PARENT/CHILD/child.txt"
|
||||
When user "Alice" deletes the file with original path "textfile1.txt" from the trashbin using the trashbin API
|
||||
Then the HTTP status code should be "405"
|
||||
And as "Alice" the file with original path "/textfile1.txt" should exist in the trashbin
|
||||
But as "Alice" the file with original path "/textfile0.txt" should exist in the trashbin
|
||||
And as "Alice" the file with original path "/PARENT/parent.txt" should exist in the trashbin
|
||||
And as "Alice" the file with original path "/PARENT/CHILD/child.txt" should exist in the trashbin
|
||||
@@ -1,125 +0,0 @@
|
||||
@api @files_versions-app-required @skipOnOcis-EOS-Storage @issue-ocis-reva-275
|
||||
|
||||
Feature: dav-versions
|
||||
|
||||
Background:
|
||||
Given using OCS API version "2"
|
||||
And using new DAV path
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-17 @issue-ocis-reva-56
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: Upload file and no version is available using various chunking methods
|
||||
When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms using the WebDAV API
|
||||
Then the version folder of file "/davtest.txt-olddav-regular" for user "Alice" should contain "0" elements
|
||||
Then the version folder of file "/davtest.txt-newdav-regular" for user "Alice" should contain "0" elements
|
||||
And as "Alice" file "/davtest.txt-olddav-oldchunking" should not exist
|
||||
And as "Alice" file "/davtest.txt-newdav-newchunking" should not exist
|
||||
|
||||
@issue-ocis-reva-17 @issue-ocis-reva-56
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: Upload a file twice and versions are available using various chunking methods
|
||||
When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms using the WebDAV API
|
||||
And user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms using the WebDAV API
|
||||
Then the version folder of file "/davtest.txt-olddav-regular" for user "Alice" should contain "1" element
|
||||
And the version folder of file "/davtest.txt-newdav-regular" for user "Alice" should contain "1" element
|
||||
And as "Alice" file "/davtest.txt-olddav-oldchunking" should not exist
|
||||
And as "Alice" file "/davtest.txt-newdav-newchunking" should not exist
|
||||
|
||||
@files_sharing-app-required
|
||||
@issue-ocis-reva-243
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: sharer of a file can see the old version information when the sharee changes the content of the file
|
||||
Given user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "First content" to "sharefile.txt"
|
||||
And user "Alice" has shared file "sharefile.txt" with user "Brian"
|
||||
When user "Brian" has uploaded file with content "Second content" to "/sharefile.txt"
|
||||
Then the HTTP status code should be "201"
|
||||
And the version folder of file "/sharefile.txt" for user "Alice" should contain "0" element
|
||||
# And the version folder of file "/sharefile.txt" for user "Alice" should contain "1" element
|
||||
|
||||
@files_sharing-app-required
|
||||
@issue-ocis-reva-243
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: sharer of a file can restore the original content of a shared file after the file has been modified by the sharee
|
||||
Given user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "First content" to "sharefile.txt"
|
||||
And user "Alice" has shared file "sharefile.txt" with user "Brian"
|
||||
And user "Brian" has uploaded file with content "Second content" to "/sharefile.txt"
|
||||
When user "Alice" restores version index "0" of file "/sharefile.txt" using the WebDAV API
|
||||
# When user "Alice" restores version index "1" of file "/sharefile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/sharefile.txt" for user "Alice" should be "First content"
|
||||
And the content of file "/sharefile.txt" for user "Brian" should be "Second content"
|
||||
# And the content of file "/sharefile.txt" for user "Brian" should be "First content"
|
||||
|
||||
@files_sharing-app-required
|
||||
@issue-ocis-reva-243 @issue-ocis-reva-386
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer
|
||||
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 a share with settings
|
||||
| path | testshare |
|
||||
| shareType | user |
|
||||
| permissions | change |
|
||||
| shareWith | Alice |
|
||||
And user "Brian" has uploaded file with content "test data 1" to "/testfile.txt"
|
||||
And user "Brian" has uploaded file with content "test data 2" to "/testfile.txt"
|
||||
And user "Brian" has uploaded file with content "test data 3" to "/testfile.txt"
|
||||
And user "Brian" moves file "/testfile.txt" to "/testshare/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/testshare/testfile.txt" for user "Alice" should be ""
|
||||
# And the content of file "/testshare/testfile.txt" for user "Alice" should be "test data 3"
|
||||
And the content of file "/testshare/testfile.txt" for user "Brian" should be "test data 3"
|
||||
And as "Brian" file "/testfile.txt" should not exist
|
||||
And as "Alice" file "/testshare/testfile.txt" should not exist
|
||||
And the content of file "/testshare/testfile.txt" for user "Brian" should be "test data 3"
|
||||
# And the version folder of file "/testshare/testfile.txt" for user "Alice" should contain "2" elements
|
||||
# And the version folder of file "/testshare/testfile.txt" for user "Brian" should contain "2" elements
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@files_sharing-app-required
|
||||
@issue-ocis-reva-243 @issue-ocis-reva-386
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer
|
||||
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 uploaded file with content "test data 1" to "/testshare/testfile.txt"
|
||||
And user "Brian" has uploaded file with content "test data 2" to "/testshare/testfile.txt"
|
||||
And user "Brian" has uploaded file with content "test data 3" to "/testshare/testfile.txt"
|
||||
And user "Brian" has created a share with settings
|
||||
| path | testshare |
|
||||
| shareType | user |
|
||||
| permissions | change |
|
||||
| shareWith | Alice |
|
||||
When user "Brian" moves file "/testshare/testfile.txt" to "/testfile.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/testfile.txt" for user "Brian" should be "test data 3"
|
||||
And as "Alice" file "/testshare/testfile.txt" should not exist
|
||||
And as "Brian" file "/testshare/testfile.txt" should not exist
|
||||
# And the version folder of file "/testfile.txt" for user "Brian" should contain "2" elements
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnStorage:ceph @files_primary_s3-issue-161 @files_sharing-app-required
|
||||
@issue-ocis-reva-376
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: Receiver tries get file versions of shared file from the sharer
|
||||
Given user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "version 1" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "version 2" to "textfile0.txt"
|
||||
And user "Alice" has uploaded file with content "version 3" to "textfile0.txt"
|
||||
And user "Alice" has shared file "textfile0.txt" with user "Brian"
|
||||
When user "Brian" tries to get versions of file "textfile0.txt" from "Alice"
|
||||
Then the HTTP status code should be "207"
|
||||
And the number of versions should be "4"
|
||||
# And the number of versions should be "3"
|
||||
@@ -1,45 +0,0 @@
|
||||
@api @issue-ocis-reva-14
|
||||
Feature: move (rename) folder
|
||||
As a user
|
||||
I want to be able to move and rename folders
|
||||
So that I can quickly manage my file system
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-reva-211
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Renaming a folder to a backslash is allowed
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "\" using the WebDAV API
|
||||
Then the HTTP status code should be "201" or "500"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-ocis-reva-211
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Renaming a folder beginning with a backslash is allowed
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "\testshare" using the WebDAV API
|
||||
Then the HTTP status code should be "201" or "500"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-ocis-reva-211
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Renaming a folder including a backslash encoded is allowed
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/hola\hola" using the WebDAV API
|
||||
Then the HTTP status code should be "201" or "500"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,22 +0,0 @@
|
||||
@api @issue-ocis-reva-14
|
||||
Feature: users cannot move (rename) a folder to a blacklisted name
|
||||
As an administrator
|
||||
I want to be able to prevent users from moving (renaming) folders to specified names
|
||||
So that I can prevent unwanted folder 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-211 @skipOnOcis-EOS-Storage @issue-ocis-reva-269 @skipOnOcis-OCIS-Storage
|
||||
# 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
|
||||
And user "Alice" has created folder "/testshare"
|
||||
When user "Alice" moves folder "/testshare" to "/.htaccess" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" folder "/.htaccess" should exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,43 +0,0 @@
|
||||
@api @issue-ocis-reva-14
|
||||
Feature: move (rename) file
|
||||
As a user
|
||||
I want to be able to move and rename files
|
||||
So that I can manage my file system
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and skeleton files
|
||||
|
||||
@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
|
||||
When user "Alice" moves file "/welcome.txt" to "/a\\a" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/a\\a" should exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@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
|
||||
When user "Alice" moves file "/welcome.txt" to "/welcome.part" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/welcome.part" should exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-211
|
||||
# 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
|
||||
Then the HTTP status code should be "201"
|
||||
And the content of file "/<renamed_file>" for user "Alice" should be ""
|
||||
Examples:
|
||||
| renamed_file |
|
||||
| #oc ab?cd=ef# |
|
||||
@@ -1,21 +0,0 @@
|
||||
@api @issue-ocis-reva-14
|
||||
Feature: users cannot move (rename) a file to a blacklisted name
|
||||
As an administrator
|
||||
I want to be able to prevent users from moving (renaming) 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 skeleton files
|
||||
|
||||
@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
|
||||
When user "Alice" moves file "/welcome.txt" to "/.htaccess" using the WebDAV API
|
||||
Then the HTTP status code should be "201"
|
||||
And as "Alice" file "/.htaccess" should exist
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,24 +0,0 @@
|
||||
@api
|
||||
Feature: download file
|
||||
As a user
|
||||
I want to be able to download files
|
||||
So that I can work wih local copies of files on my client system
|
||||
|
||||
Background:
|
||||
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"
|
||||
And user "Alice" has uploaded file with content "Welcome this is just an example file for developers." to "/welcome.txt"
|
||||
|
||||
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-98
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Get the content-length response header of a pdf file
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file "filesForUpload/simple.pdf" to "/simple.pdf"
|
||||
When user "Alice" downloads file "/simple.pdf" using the WebDAV API
|
||||
And the following headers should not be set
|
||||
| header |
|
||||
| OC-JobStatus-Location |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,22 +0,0 @@
|
||||
@api
|
||||
Feature: refuse access
|
||||
As an administrator
|
||||
I want to refuse access to unauthenticated and disabled users
|
||||
So that I can secure the system
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Unauthenticated call
|
||||
Given using <dav_version> DAV path
|
||||
When an unauthenticated client connects to the dav endpoint using the WebDAV API
|
||||
Then the HTTP status code should be "401"
|
||||
And there should be no duplicate headers
|
||||
And the following headers should be set
|
||||
| header | value |
|
||||
| WWW-Authenticate | Basic realm="%base_url_without_scheme%" |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,112 +0,0 @@
|
||||
@api @issue-ocis-187
|
||||
Feature: previews of files downloaded through the webdav API
|
||||
|
||||
Background:
|
||||
Given user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@issue-ocis-188
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: download previews with invalid width
|
||||
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 "32" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
Examples:
|
||||
| width |
|
||||
| 0 |
|
||||
| 0.5 |
|
||||
| -1 |
|
||||
| false |
|
||||
| true |
|
||||
| A |
|
||||
| %2F |
|
||||
|
||||
@issue-ocis-188
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: download previews with invalid height
|
||||
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 "<height>" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
Examples:
|
||||
| height |
|
||||
| 0 |
|
||||
| 0.5 |
|
||||
| -1 |
|
||||
| false |
|
||||
| true |
|
||||
| A |
|
||||
| %2F |
|
||||
|
||||
@issue-ocis-189
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: download previews of file types that don't support preview
|
||||
Given user "Alice" has uploaded file "filesForUpload/<filename>" to "/<newfilename>"
|
||||
When user "Alice" downloads the preview of "/<newfilename>" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
Examples:
|
||||
| filename | newfilename |
|
||||
| simple.pdf | test.pdf |
|
||||
| simple.odt | test.odt |
|
||||
| new-data.zip | test.zip |
|
||||
|
||||
@issue-ocis-187
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: download previews of different image file types
|
||||
Given user "Alice" has uploaded file "filesForUpload/<imageName>" to "/<newImageName>"
|
||||
When user "Alice" downloads the preview of "/<newImageName>" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
And the downloaded image should be "1240" pixels wide and "648" pixels high
|
||||
Examples:
|
||||
| imageName | newImageName |
|
||||
| testavatar.jpg | testimage.jpg |
|
||||
| testavatar.png | testimage.png |
|
||||
|
||||
@issue-ocis-187
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: download previews of image after renaming it
|
||||
Given user "Alice" has uploaded file "filesForUpload/testavatar.jpg" to "/testimage.jpg"
|
||||
When user "Alice" moves file "/testimage.jpg" to "/testimage.txt" using the WebDAV API
|
||||
And user "Alice" downloads the preview of "/testimage.txt" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
And the downloaded image should be "1240" pixels wide and "648" pixels high
|
||||
|
||||
@issue-ocis-thumbnails-191 @skipOnOcis-EOS-Storage @issue-ocis-reva-308
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: download previews of other users files
|
||||
Given user "Brian" has been created with default attributes and without skeleton files
|
||||
And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When user "Brian" downloads the preview of "/parent.txt" of "Alice" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "200"
|
||||
|
||||
@issue-ocis-190
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: download previews of folders
|
||||
Given user "Alice" has created folder "subfolder"
|
||||
When user "Alice" downloads the preview of "/subfolder/" with width "32" and height "32" using the WebDAV API
|
||||
Then the HTTP status code should be "501"
|
||||
|
||||
@issue-ocis-192
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: Download file previews when it is disabled by the administrator
|
||||
Given the administrator has updated system config key "enable_previews" with value "false" and type "boolean"
|
||||
And 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 "200"
|
||||
|
||||
@issue-ocis-193
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: unset maximum size of previews
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
And the administrator has updated system config key "preview_max_x" with value "null"
|
||||
And the administrator has updated system config key "preview_max_y" with value "null"
|
||||
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 "200"
|
||||
|
||||
@issue-ocis-193
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario: set maximum size of previews
|
||||
Given user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
|
||||
When the administrator updates system config key "preview_max_x" with value "null" using the occ command
|
||||
And the administrator updates system config key "preview_max_y" with value "null" using the occ command
|
||||
Then the HTTP status code should be "201"
|
||||
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 "200"
|
||||
@@ -1,37 +0,0 @@
|
||||
@api
|
||||
Feature: create folder
|
||||
As a user
|
||||
I want to be able to create folders
|
||||
So that I can organise the files in my file system
|
||||
|
||||
Background:
|
||||
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 @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
|
||||
And user "Alice" has created folder "my-data"
|
||||
When user "Alice" creates folder "my-data" using the WebDAV API
|
||||
Then the HTTP status code should be "405"
|
||||
And as "Alice" folder "my-data" should exist
|
||||
And the body of the response should be empty
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-ocis-reva-168
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: try to create a folder with a name of an existing file
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has uploaded file with content "uploaded data" to "/my-data.txt"
|
||||
When user "Alice" creates folder "my-data.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "405"
|
||||
And the body of the response should be empty
|
||||
And the content of file "/my-data.txt" for user "Alice" should be "uploaded data"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,21 +0,0 @@
|
||||
@api @issue-ocis-reva-57
|
||||
Feature: set file properties
|
||||
As a user
|
||||
I want to be able to set meta-information about files
|
||||
So that I can reccord file meta-information (detailed requirement TBD)
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@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
|
||||
And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/testcustomprop.txt"
|
||||
When user "Alice" sets property "very-custom-prop" with namespace "x1='http://whatever.org/ns'" of file "/testcustomprop.txt" to "veryCustomPropValue" using the WebDAV API
|
||||
Then the HTTP status code should be "500"
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
@@ -1,115 +0,0 @@
|
||||
@api
|
||||
Feature: get file properties
|
||||
As a user
|
||||
I want to be able to get meta-information about files
|
||||
So that I can know file meta-information (detailed requirement TBD)
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@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
|
||||
And user "Alice" has uploaded file with content "uploaded content" to "<file_name>"
|
||||
When user "Alice" gets the properties of file "<file_name>" using the WebDAV API
|
||||
Then the properties response should contain an etag
|
||||
And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>/"
|
||||
Examples:
|
||||
| dav_version | file_name | expected_href |
|
||||
| old | /C++ file.cpp | webdav\/C\+\+%20file\.cpp |
|
||||
| old | /file #2.txt | webdav\/file%20%232\.txt |
|
||||
| old | /file &2.txt | webdav\/file%20&2\.txt |
|
||||
| new | /C++ file.cpp | dav\/files\/%username%\/C\+\+%20file\.cpp |
|
||||
| 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 @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
|
||||
And user "Alice" has uploaded file with content "uploaded content" to "<file_name>"
|
||||
When user "Alice" gets the properties of file "<file_name>" using the WebDAV API
|
||||
Then the properties response should contain an etag
|
||||
And the value of the item "//d:response/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>/"
|
||||
Examples:
|
||||
| dav_version | file_name | expected_href |
|
||||
| old | /file ?2.txt | webdav\/file%20%3F2\.txt |
|
||||
| new | /file ?2.txt | dav\/files\/%username%\/file%20%3F2\.txt |
|
||||
|
||||
@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 to content
|
||||
Given using <dav_version> DAV path
|
||||
When user "Alice" uploads file with content "uploaded content" to "<file_name>" using the WebDAV API
|
||||
Then the HTTP status code should be "500"
|
||||
Examples:
|
||||
| dav_version | file_name |
|
||||
| old | /file ?2.txt |
|
||||
| new | /file ?2.txt |
|
||||
|
||||
@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
|
||||
And user "Alice" has created folder "<folder_name>"
|
||||
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file1.txt"
|
||||
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file2.txt"
|
||||
When user "Alice" gets the properties of folder "<folder_name>" with depth 1 using the WebDAV API
|
||||
Then the value of the item "//d:response[1]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\//"
|
||||
And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file1.txt/"
|
||||
And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file2.txt/"
|
||||
Examples:
|
||||
| dav_version | folder_name | expected_href |
|
||||
| old | /upload | webdav\/upload |
|
||||
| old | /strängé folder | webdav\/str%C3%A4ng%C3%A9%20folder |
|
||||
| old | /C++ folder | webdav\/C\+\+%20folder |
|
||||
| old | /नेपाली | webdav\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 |
|
||||
| old | /folder #2.txt | webdav\/folder%20%232\.txt |
|
||||
| old | /folder &2.txt | webdav\/folder%20&2\.txt |
|
||||
| new | /upload | dav\/files\/%username%\/upload |
|
||||
| new | /strängé folder | dav\/files\/%username%\/str%C3%A4ng%C3%A9%20folder |
|
||||
| new | /C++ folder | dav\/files\/%username%\/C\+\+%20folder |
|
||||
| new | /नेपाली | dav\/files\/%username%\/%E0%A4%A8%E0%A5%87%E0%A4%AA%E0%A4%BE%E0%A4%B2%E0%A5%80 |
|
||||
| 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 @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
|
||||
And user "Alice" has created folder "<folder_name>"
|
||||
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file1.txt"
|
||||
And user "Alice" has uploaded file with content "uploaded content" to "<folder_name>/file2.txt"
|
||||
When user "Alice" gets the properties of folder "<folder_name>" with depth 1 using the WebDAV API
|
||||
Then the value of the item "//d:response[1]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\//"
|
||||
And the value of the item "//d:response[2]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file1.txt/"
|
||||
And the value of the item "//d:response[3]/d:href" in the response to user "Alice" should match "/remote\.php\/<expected_href>\/file2.txt/"
|
||||
Examples:
|
||||
| dav_version | folder_name | expected_href |
|
||||
| old | /folder ?2.txt | webdav\/folder%20%3F2\.txt |
|
||||
| new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt |
|
||||
|
||||
@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
|
||||
And user "Alice" has created folder "/folder ?2.txt"
|
||||
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 |
|
||||
| /folder ?2.txt/file1.txt | 500 | no |
|
||||
Examples:
|
||||
| dav_version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-ocis-reva-163
|
||||
# after fixing all issues delete this Scenario and use the one from oC10 core
|
||||
Scenario Outline: Do a PROPFIND to a non-existing URL
|
||||
And user "Alice" requests "<url>" with "PROPFIND" using basic auth
|
||||
Then the body of the response should be empty
|
||||
Examples:
|
||||
| url |
|
||||
| /remote.php/dav/files/does-not-exist |
|
||||
| /remote.php/dav/does-not-exist |
|
||||
@@ -1,39 +0,0 @@
|
||||
@api
|
||||
Feature: upload file
|
||||
As a user
|
||||
I want to be able to upload files
|
||||
So that I can store and share files between multiple client systems
|
||||
|
||||
Background:
|
||||
Given using OCS API version "1"
|
||||
And user "Alice" has been created with default attributes and without skeleton files
|
||||
|
||||
@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
|
||||
When user "Alice" uploads file with content "uploaded content" to <file_name> using the WebDAV API
|
||||
Then the content of file <file_name> for user "Alice" should be ""
|
||||
Examples:
|
||||
| dav_version | file_name |
|
||||
| old | "file ?2.txt" |
|
||||
| new | "file ?2.txt" |
|
||||
|
||||
@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
|
||||
Given using <dav_version> DAV path
|
||||
And user "Alice" has created folder "/upload"
|
||||
And user "Alice" has stored etag of element "/<element>"
|
||||
When user "Alice" uploads file with content "uploaded content" to "/upload/file.txt" using the WebDAV API
|
||||
Then the content of file "/upload/file.txt" for user "Alice" should be "uploaded content"
|
||||
# And the etag of element "/<element>" of user "Alice" should have changed
|
||||
And the etag of element "/<element>" of user "Alice" should not have changed
|
||||
Examples:
|
||||
| dav_version | element |
|
||||
| old | |
|
||||
| old | upload |
|
||||
| new | |
|
||||
# this example is intermittent - sometimes the etag changes and sometimes not
|
||||
# | new | upload |
|
||||
@@ -1,40 +0,0 @@
|
||||
<?php
|
||||
|
||||
use Behat\Behat\Context\Context;
|
||||
use Behat\Behat\Hook\Scope\BeforeScenarioScope;
|
||||
use TestHelpers\AppConfigHelper;
|
||||
use TestHelpers\SetupHelper;
|
||||
|
||||
require_once 'bootstrap.php';
|
||||
|
||||
/**
|
||||
* Context for Reva specific steps
|
||||
*/
|
||||
class RevaContext implements Context {
|
||||
|
||||
/**
|
||||
* @var FeatureContext
|
||||
*/
|
||||
private $featureContext;
|
||||
|
||||
/**
|
||||
* @BeforeScenario
|
||||
*
|
||||
* @param BeforeScenarioScope $scope
|
||||
*
|
||||
* @return void
|
||||
* @throws Exception
|
||||
*/
|
||||
public function setUpScenario(BeforeScenarioScope $scope) {
|
||||
// Get the environment
|
||||
$environment = $scope->getEnvironment();
|
||||
// Get all the contexts you need in this context
|
||||
$this->featureContext = $environment->getContext('FeatureContext');
|
||||
SetupHelper::init(
|
||||
$this->featureContext->getAdminUsername(),
|
||||
$this->featureContext->getAdminPassword(),
|
||||
$this->featureContext->getBaseUrl(),
|
||||
$this->featureContext->getOcPath()
|
||||
);
|
||||
}
|
||||
}
|
||||
@@ -1,14 +0,0 @@
|
||||
<?php
|
||||
$pathToCore = \getenv('PATH_TO_CORE');
|
||||
if ($pathToCore === false) {
|
||||
$pathToCore = "../core";
|
||||
}
|
||||
|
||||
require_once $pathToCore . '/tests/acceptance/features/bootstrap/bootstrap.php';
|
||||
|
||||
$classLoader = new \Composer\Autoload\ClassLoader();
|
||||
$classLoader->addPsr4(
|
||||
"", $pathToCore . "/tests/acceptance/features/bootstrap", true
|
||||
);
|
||||
|
||||
$classLoader->register();
|
||||
@@ -1,19 +0,0 @@
|
||||
{
|
||||
"server": "http://reva-server:9140",
|
||||
"theme": "owncloud",
|
||||
"version": "0.1.0",
|
||||
"openIdConnect": {
|
||||
"metadata_url": "https://konnectd:9130/.well-known/openid-configuration",
|
||||
"authority": "https://konnectd:9130",
|
||||
"client_id": "phoenix",
|
||||
"response_type": "code",
|
||||
"scope": "openid profile email"
|
||||
},
|
||||
"apps": [
|
||||
"files",
|
||||
"draw-io",
|
||||
"pdf-viewer",
|
||||
"markdown-editor",
|
||||
"media-viewer"
|
||||
]
|
||||
}
|
||||
@@ -1,16 +0,0 @@
|
||||
---
|
||||
|
||||
# OpenID Connect client registry.
|
||||
clients:
|
||||
- id: phoenix
|
||||
name: OCIS
|
||||
application_type: web
|
||||
insecure: yes
|
||||
trusted: yes
|
||||
redirect_uris:
|
||||
- http://phoenix:9100/oidc-callback.html
|
||||
- http://phoenix:9100/
|
||||
origins:
|
||||
- http://phoenix:9100
|
||||
|
||||
authorities:
|
||||
@@ -1,49 +0,0 @@
|
||||
dn: ou=TestUsers,dc=owncloud,dc=com
|
||||
objectclass: top
|
||||
objectclass: organizationalUnit
|
||||
ou: TestUsers
|
||||
|
||||
dn: ou=TestGroups,dc=owncloud,dc=com
|
||||
objectclass: top
|
||||
objectclass: organizationalUnit
|
||||
ou: TestGroups
|
||||
|
||||
dn: cn=grp1,ou=TestGroups,dc=owncloud,dc=com
|
||||
cn: grp1
|
||||
gidnumber: 500
|
||||
memberuid: tu1
|
||||
memberuid: tu2
|
||||
objectclass: top
|
||||
objectclass: posixGroup
|
||||
|
||||
dn: uid=tu1,ou=TestUsers,dc=owncloud,dc=com
|
||||
cn: TU1
|
||||
sn: Owane
|
||||
displayname: User Owane
|
||||
gecos: TU1
|
||||
gidnumber: 5000
|
||||
givenname: TU1
|
||||
homedirectory: /home/openldap/tu1
|
||||
loginshell: /bin/bash
|
||||
mail: tu1@example.org
|
||||
objectclass: posixAccount
|
||||
objectclass: inetOrgPerson
|
||||
uid: tu1
|
||||
uidnumber: 30001
|
||||
userpassword: 1234
|
||||
|
||||
dn: uid=tu2,ou=TestUsers,dc=owncloud,dc=com
|
||||
cn: TU2
|
||||
sn: Towu
|
||||
displayname: User Towu
|
||||
gecos: TU2
|
||||
gidnumber: 5000
|
||||
givenname: TU2
|
||||
homedirectory: /home/openldap/tu2
|
||||
loginshell: /bin/bash
|
||||
mail: tu2@example.org
|
||||
objectclass: posixAccount
|
||||
objectclass: inetOrgPerson
|
||||
uid: tu2
|
||||
uidnumber: 30002
|
||||
userpassword: AaBb2Cc3Dd4
|
||||
@@ -1,23 +0,0 @@
|
||||
{
|
||||
"config" : {
|
||||
"platform": {
|
||||
"php": "7.2"
|
||||
}
|
||||
},
|
||||
"require": {
|
||||
"behat/behat": "^3.7",
|
||||
"behat/mink": "1.7.1",
|
||||
"behat/mink-extension": "^2.3",
|
||||
"behat/mink-goutte-driver": "^1.2",
|
||||
"behat/mink-selenium2-driver": "^1.4",
|
||||
"ciaranmcnulty/behat-stepthroughextension" : "dev-master",
|
||||
"jarnaiz/behat-junit-formatter": "^1.3",
|
||||
"rdx/behat-variables": "^1.2",
|
||||
"sensiolabs/behat-page-object-extension": "^2.3",
|
||||
"symfony/translation": "^4.4",
|
||||
"sabre/xml": "^2.2",
|
||||
"guzzlehttp/guzzle": "^6.5",
|
||||
"phpunit/phpunit": "^8.5",
|
||||
"laminas/laminas-ldap": "^2.10"
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user