mirror/opencloud
1
0
Fork 0
mirror of https://github.com/opencloud-eu/opencloud.git synced 2026-03-04 15:27:17 -05:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into autoincrement-index

Browse Source
This commit is contained in:
A.Unger
2020-10-19 14:47:43 +02:00
parent 1bf3896107 1278909e3f
commit b55ba64488
27 changed files with 261 additions and 264 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
.drone.star
View File

@@ -15,12 +15,12 @@ config = {
},
'apiTests': {
'coreBranch': 'master',
'coreCommit': '0d2e3d07f52b10245521e1c29c8c7faeb6387b23',
'coreCommit': '1df47648f944ab21521f6c8d538dc183e1e8f1ea',
'numberOfParts': 6
},
'uiTests': {
'phoenixBranch': 'master',
'phoenixCommit': '1e278d85962cdd172886aeb222532f72c3972774',
'phoenixCommit': '693fa6d275243fc860b4b82e5146d25f62d927fb',
'suites': {
'phoenixWebUI1': [
'webUICreateFilesFolders',
@@ -342,7 +342,8 @@ def localApiTests(ctx, coreBranch = 'master', coreCommit = '', storage = 'ownclo
'pull': 'always',
'environment' : {
'TEST_SERVER_URL': 'https://ocis-server:9200',
'OCIS_REVA_DATA_ROOT': '%s' % ('/srv/app/tmp/ocis/owncloud/' if storage == 'owncloud' else ''),
'OCIS_REVA_DATA_ROOT': '%s' % ('/srv/app/tmp/ocis/owncloud/data/' if storage == 'owncloud' else ''),
'STORAGE_DRIVER': '%s' % ('OWNCLOUD' if storage == 'owncloud' else 'OCIS'),
'DELETE_USER_DATA_CMD': '%s' % ('' if storage == 'owncloud' else 'rm -rf /srv/app/tmp/ocis/storage/users/nodes/root/*'),
'SKELETON_DIR': '/srv/app/tmp/testing/data/apiSkeleton',
'OCIS_SKELETON_STRATEGY': '%s' % ('copy' if storage == 'owncloud' else 'upload'),
@@ -396,7 +397,8 @@ def coreApiTests(ctx, coreBranch = 'master', coreCommit = '', part_number = 1, n
'pull': 'always',
'environment' : {
'TEST_SERVER_URL': 'https://ocis-server:9200',
'OCIS_REVA_DATA_ROOT': '%s' % ('/srv/app/tmp/ocis/owncloud/' if storage == 'owncloud' else ''),
'OCIS_REVA_DATA_ROOT': '%s' % ('/srv/app/tmp/ocis/owncloud/data/' if storage == 'owncloud' else ''),
'STORAGE_DRIVER': '%s' % ('OWNCLOUD' if storage == 'owncloud' else 'OCIS'),
'DELETE_USER_DATA_CMD': '%s' % ('' if storage == 'owncloud' else 'rm -rf /srv/app/tmp/ocis/storage/users/nodes/root/*'),
'SKELETON_DIR': '/srv/app/tmp/testing/data/apiSkeleton',
'OCIS_SKELETON_STRATEGY': '%s' % ('copy' if storage == 'owncloud' else 'upload'),
@@ -565,8 +567,7 @@ def accountsUITests(ctx, phoenixBranch, phoenixCommitId, storage):
'PHOENIX_WEB_CONFIG': '/drone/src/accounts/ui/tests/config/drone/ocis-config.json',
'KONNECTD_IDENTIFIER_REGISTRATION_CONF': '/drone/src/accounts/ui/tests/config/drone/identifier-registration.yml',
'KONNECTD_ISS': 'https://ocis-server:9200',
#'STORAGE_STORAGE_METADATA_ROOT': '/srv/app/tmp/ocis/storage/users',
#'ACCOUNTS_STORAGE_DISK_PATH': '/srv/app/tmp/ocis-accounts', # Temporary workaround, don't use metadata storage
'ACCOUNTS_STORAGE_DISK_PATH': '/srv/app/tmp/ocis-accounts', # Temporary workaround, don't use metadata storage
},
'commands': [
'mkdir -p /srv/app/tmp/reva',
@@ -788,7 +789,6 @@ def dockerEos(ctx):
},
'auto_tag': True,
'context': 'ocis/docker/eos-ocis',
'auto_tag_suffix': 'linux-amd64',
'dockerfile': 'ocis/docker/eos-ocis/Dockerfile',
'repo': 'owncloud/eos-ocis',
},
@@ -1427,7 +1427,7 @@ def ocisServer(storage):
'KONNECTD_IDENTIFIER_REGISTRATION_CONF': '/drone/src/ocis/tests/config/drone/identifier-registration.yml',
'KONNECTD_ISS': 'https://ocis-server:9200',
'KONNECTD_TLS': 'true',
#'ACCOUNTS_DATA_PATH': '/srv/app/tmp/ocis-accounts/',
'ACCOUNTS_DATA_PATH': '/srv/app/tmp/ocis-accounts/',
},
'commands': [
'apk add mailcap', # install /etc/mime.types

10
CHANGELOG.md
View File

@@ -18,6 +18,7 @@
* Change - Switch over to a new custom-built runtime: [#287](https://github.com/owncloud/ocis/pull/287)
* Change - Account management permissions for Admin role: [#124](https://github.com/owncloud/product/issues/124)
* Change - Update phoenix to v0.18.0: [#651](https://github.com/owncloud/ocis/pull/651)
* Change - Default apps in ownCloud Web: [#688](https://github.com/owncloud/ocis/pull/688)
* Change - Make ocis-settings available: [#287](https://github.com/owncloud/ocis/pull/287)
* Change - Start ocis-proxy with the ocis server command: [#119](https://github.com/owncloud/ocis/issues/119)
* Change - Update phoenix to v0.20.0: [#674](https://github.com/owncloud/ocis/pull/674)
@@ -210,6 +211,15 @@
https://github.com/owncloud/phoenix/releases/tag/v0.18.0
https://github.com/owncloud/owncloud-design-system/releases/tag/v1.12.1
* Change - Default apps in ownCloud Web: [#688](https://github.com/owncloud/ocis/pull/688)
Tags: web
We changed the default apps for ownCloud Web to be only files and media-viewer.
Markdown-editor and draw-io have been removed as defaults.
https://github.com/owncloud/ocis/pull/688
* Change - Make ocis-settings available: [#287](https://github.com/owncloud/ocis/pull/287)
Tags: settings

6
accounts/pkg/assets/embed.go
View File

File diff suppressed because one or more lines are too long

2
accounts/ui/app.js
View File

@@ -28,7 +28,7 @@ const navItems = [
name: 'accounts',
path: `/${appInfo.id}/`
},
menu: 'user'
menu: 'apps'
}
]

12
accounts/yarn.lock
View File

@@ -1467,9 +1467,9 @@ binary-extensions@^2.0.0:
integrity sha512-1Yj8h9Q+QDF5FzhMs/c9+6UntbD5MkRfRwac8DoEm9ZfUBZ7tZ55YcGVAzEe4bXsdQHEk+s9S5wsOKVdZrw0tQ==
bl@^4.0.1:
version "4.0.2"
resolved "https://registry.yarnpkg.com/bl/-/bl-4.0.2.tgz#52b71e9088515d0606d9dd9cc7aa48dc1f98e73a"
integrity sha512-j4OH8f6Qg2bGuWfRiltT2HYGx0e1QcBTrK9KAHNMwMZdQnDZFk0ZSYIpADjYCB3U12nicC5tVJwSIhwOWjb4RQ==
version "4.0.3"
resolved "https://registry.yarnpkg.com/bl/-/bl-4.0.3.tgz#12d6287adc29080e22a705e5764b2a9522cdc489"
integrity sha512-fs4G6/Hu4/EE+F75J8DuN/0IpQqNjAdC7aEQv7Qt8MHGUH7Ckv2MwTEEeN9QehD0pfIDkMI1bkHYkKy7xHyKIg==
dependencies:
buffer "^5.5.0"
inherits "^2.0.4"
@@ -4163,9 +4163,9 @@ lodash.union@^4.6.0:
integrity sha1-SLtQiECfFvGCFmZkHETdGqrjzYg=
lodash@^4.15.0, lodash@^4.17.13, lodash@^4.17.14, lodash@^4.17.15, lodash@^4.17.4:
version "4.17.15"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.15.tgz#b447f6670a0455bbfeedd11392eff330ea097548"
integrity sha512-8xOcRHvCjnocdS5cpwXQXVzmmh5e5+saE2QGoeQmbKmRS6J3VQppPOIt0MnmE+4xlZoumy0GPG0D0MVIQbNA1A==
version "4.17.20"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.20.tgz#b44a9b6297bcb698f1c51a3545a2b3b368d59c52"
integrity sha512-PlhdFcillOINfeV7Ni6oF1TAEayyZBoZ8bcshTHqOYJYlrqzRK5hagpagky5o4HfCzzd1TRkXPMFq6cKk9rGmA==
log-symbols@2.2.0:
version "2.2.0"

7
changelog/unreleased/phoenix-default-apps.md Normal file
View File

@@ -0,0 +1,7 @@
Change: Default apps in ownCloud Web
Tags: web
We changed the default apps for ownCloud Web to be only files and media-viewer. Markdown-editor and draw-io have been removed as defaults.
https://github.com/owncloud/ocis/pull/688

19
docs/ocis/development/testing.md
View File

@@ -45,7 +45,7 @@ Then run the api acceptance tests with the following command:
make test-acceptance-api \
TEST_SERVER_URL=https://localhost:9200 \
TEST_OCIS=true \
OCIS_REVA_DATA_ROOT=/var/tmp/reva/ \
OCIS_REVA_DATA_ROOT=/var/tmp/ocis/owncloud/ \
SKELETON_DIR=apps/testing/data/apiSkeleton \
BEHAT_FILTER_TAGS='~@notToImplementOnOCIS&&~@toImplementOnOCIS'
```
@@ -59,13 +59,14 @@ To run a single test add `BEHAT_FEATURE=<feature file>`
### use existing tests for BDD
As a lot of scenarios are written for oC10, we can use those tests for Behaviour driven development in ocis.
Every scenario that does not work in OCIS with OC storage, is listed in `tests/acceptance/expected-failures-on-OC-storage.txt` with a link to the related issue.
Every scenario that does not work in OCIS with "owncloud" storage, is listed in `ocis/tests/acceptance/expected-failures-on-OWNCLOUD-storage.txt` with a link to the related issue.
Every scenario that does not work in OCIS with "ocis" storage, is listed in `ocis/tests/acceptance/expected-failures-on-OCIS-storage.txt` with a link to the related issue.
Those scenarios are run in the ordinary acceptance test pipeline in CI. The scenarios that fail are checked against the
expected failures. If there are any differences then the CI pipeline fails.
Similarly, scenarios that do not work in OCIS with EOS storage are listed in `tests/acceptance/expected-failures-on-EOS-storage.txt`.
Similarly, scenarios that do not work in OCIS with EOS storage are listed in `ocis/tests/acceptance/expected-failures-on-EOS-storage.txt`.
Additionally, some issues have scenarios that demonstrate the current buggy behaviour in ocis(reva).
Those scenarios are in this ocis repository in `tests/acceptance/features/apiOcisSpecific`.
Those scenarios are in this ocis repository in `ocis/tests/acceptance/features/apiOcisSpecific`.
Have a look into the [documentation](https://doc.owncloud.com/server/developer_manual/testing/acceptance-tests.html#writing-scenarios-for-bugs) to understand why we are writing those tests.
If you want to work on a specific issue
@@ -77,7 +78,7 @@ If you want to work on a specific issue
'apiTests': {
'coreBranch': 'master',
'coreCommit': 'a06b1bd5ba8e5244bfaf7fa04f441961e6fb0daa',
'numberOfParts': 2
'numberOfParts': 6
}
}
@@ -88,7 +89,7 @@ If you want to work on a specific issue
make test-acceptance-api \
TEST_SERVER_URL=https://localhost:9200 \
TEST_OCIS=true \
OCIS_REVA_DATA_ROOT=/var/tmp/reva/ \
OCIS_REVA_DATA_ROOT=/var/tmp/ocis/owncloud/ \
BEHAT_FEATURE='tests/acceptance/features/apiComments/comments.feature:123'
```
@@ -99,9 +100,3 @@ If you want to work on a specific issue
7. run each of the local tests that were demonstrating the **buggy** behavior. They should fail.
8. delete each of the local tests that were demonstrating the **buggy** behavior.
9. make a PR that has the fixed code, relevant lines removed from the expected failures file and bug demonstration tests deleted.
If the changes also affect the `ocis-reva` repository make sure the changes get ported over there.
### Notes
- in a normal case the test-code cleans up users after the test-run, but if a test-run is interrupted (e.g. by CTRL+C) users might have been left on the LDAP server. In that case rerunning the tests requires wiping the users in the ldap server, otherwise the tests will fail when trying to populate the users.
- the tests usually create users in the OU `TestUsers` with usernames specified in the feature file. If not defined in the feature file, most users have the password `123456`, defined by `regularUserPassword` in `behat.yml`, but other passwords are also used, see [`\FeatureContext::getPasswordForUser()`](https://github.com/owncloud/core/blob/master/tests/acceptance/features/bootstrap/FeatureContext.php#L386) for mapping and [`\FeatureContext::__construct`](https://github.com/owncloud/core/blob/master/tests/acceptance/features/bootstrap/FeatureContext.php#L1668) for the password definitions.

2
ocis-phoenix/pkg/flagset/flagset.go
View File

@@ -173,7 +173,7 @@ func ServerWithConfig(cfg *config.Config) []cli.Flag {
},
&cli.StringSliceFlag{
Name: "web-config-app",
Value: cli.NewStringSlice("files", "draw-io", "markdown-editor", "media-viewer"),
Value: cli.NewStringSlice("files", "media-viewer"),
Usage: `--web-config-app files [--web-config-app draw-io]`,
EnvVars: []string{"PHOENIX_WEB_CONFIG_APPS"},
},

111
ocis/tests/acceptance/expected-failures-on-OCIS-storage.txt
View File

@@ -381,10 +381,6 @@ apiShareManagementBasicToShares/deleteShareFromShares.feature:46
#
apiShareManagementBasicToShares/createShareToSharesFolder.feature:100
apiShareManagementBasicToShares/createShareToSharesFolder.feature:101
apiShareManagementBasicToShares/createShareToSharesFolder.feature:115
apiShareManagementBasicToShares/createShareToSharesFolder.feature:116
apiShareManagementBasicToShares/createShareToSharesFolder.feature:130
apiShareManagementBasicToShares/createShareToSharesFolder.feature:131
#
# https://github.com/owncloud/ocis-reva/issues/34 groups endpoint does not exist
#
@@ -978,75 +974,72 @@ apiTrashbin/trashbinFilesFolders.feature:45
apiTrashbin/trashbinFilesFolders.feature:60
apiTrashbin/trashbinFilesFolders.feature:61
#
# https://github.com/owncloud/core/issues/38006 Review and fix the tests that have sharing step to work with ocis
#
apiTrashbin/trashbinFilesFolders.feature:89
apiTrashbin/trashbinFilesFolders.feature:90
apiTrashbin/trashbinFilesFolders.feature:104
apiTrashbin/trashbinFilesFolders.feature:105
#
# https://github.com/owncloud/product/issues/273 invalid webdav responses for unauthorized requests.
#
apiTrashbin/trashbinFilesFolders.feature:184
apiTrashbin/trashbinFilesFolders.feature:185
apiTrashbin/trashbinFilesFolders.feature:202
apiTrashbin/trashbinFilesFolders.feature:203
apiTrashbin/trashbinFilesFolders.feature:226
apiTrashbin/trashbinFilesFolders.feature:227
apiTrashbin/trashbinFilesFolders.feature:240
apiTrashbin/trashbinFilesFolders.feature:241
apiTrashbin/trashbinFilesFolders.feature:254
apiTrashbin/trashbinFilesFolders.feature:255
apiTrashbin/trashbinFilesFolders.feature:154
apiTrashbin/trashbinFilesFolders.feature:155
apiTrashbin/trashbinFilesFolders.feature:172
apiTrashbin/trashbinFilesFolders.feature:173
apiTrashbin/trashbinFilesFolders.feature:196
apiTrashbin/trashbinFilesFolders.feature:197
apiTrashbin/trashbinFilesFolders.feature:210
apiTrashbin/trashbinFilesFolders.feature:211
apiTrashbin/trashbinFilesFolders.feature:224
apiTrashbin/trashbinFilesFolders.feature:225
#
# https://github.com/owncloud/product/issues/187
# Cannot create user with different username and emails
#
apiTrashbin/trashbinFilesFolders.feature:269
apiTrashbin/trashbinFilesFolders.feature:270
apiTrashbin/trashbinFilesFolders.feature:271
apiTrashbin/trashbinFilesFolders.feature:275
apiTrashbin/trashbinFilesFolders.feature:276
apiTrashbin/trashbinFilesFolders.feature:277
apiTrashbin/trashbinFilesFolders.feature:239
apiTrashbin/trashbinFilesFolders.feature:240
apiTrashbin/trashbinFilesFolders.feature:241
apiTrashbin/trashbinFilesFolders.feature:245
apiTrashbin/trashbinFilesFolders.feature:246
apiTrashbin/trashbinFilesFolders.feature:247
#
# https://github.com/owncloud/core/issues/38006 Review and fix the tests that have sharing step to work with ocis
#
apiTrashbin/trashbinRestore.feature:31
apiTrashbin/trashbinRestore.feature:32
apiTrashbin/trashbinRestore.feature:40
apiTrashbin/trashbinRestore.feature:41
#
# https://github.com/owncloud/ocis-reva/issues/117 cannot restore trashbin item
#
apiTrashbin/trashbinRestore.feature:62
apiTrashbin/trashbinRestore.feature:63
apiTrashbin/trashbinRestore.feature:76
apiTrashbin/trashbinRestore.feature:77
apiTrashbin/trashbinRestore.feature:54
apiTrashbin/trashbinRestore.feature:55
apiTrashbin/trashbinRestore.feature:70
apiTrashbin/trashbinRestore.feature:71
apiTrashbin/trashbinRestore.feature:90
apiTrashbin/trashbinRestore.feature:91
apiTrashbin/trashbinRestore.feature:92
apiTrashbin/trashbinRestore.feature:93
apiTrashbin/trashbinRestore.feature:112
apiTrashbin/trashbinRestore.feature:113
apiTrashbin/trashbinRestore.feature:114
apiTrashbin/trashbinRestore.feature:115
apiTrashbin/trashbinRestore.feature:116
apiTrashbin/trashbinRestore.feature:117
apiTrashbin/trashbinRestore.feature:140
apiTrashbin/trashbinRestore.feature:141
apiTrashbin/trashbinRestore.feature:142
apiTrashbin/trashbinRestore.feature:143
apiTrashbin/trashbinRestore.feature:160
apiTrashbin/trashbinRestore.feature:161
apiTrashbin/trashbinRestore.feature:179
apiTrashbin/trashbinRestore.feature:180
apiTrashbin/trashbinRestore.feature:197
apiTrashbin/trashbinRestore.feature:198
apiTrashbin/trashbinRestore.feature:270
apiTrashbin/trashbinRestore.feature:271
apiTrashbin/trashbinRestore.feature:314
apiTrashbin/trashbinRestore.feature:315
apiTrashbin/trashbinRestore.feature:316
apiTrashbin/trashbinRestore.feature:317
apiTrashbin/trashbinRestore.feature:318
apiTrashbin/trashbinRestore.feature:319
apiTrashbin/trashbinRestore.feature:334
apiTrashbin/trashbinRestore.feature:335
apiTrashbin/trashbinRestore.feature:94
apiTrashbin/trashbinRestore.feature:95
apiTrashbin/trashbinRestore.feature:118
apiTrashbin/trashbinRestore.feature:119
apiTrashbin/trashbinRestore.feature:120
apiTrashbin/trashbinRestore.feature:121
apiTrashbin/trashbinRestore.feature:138
apiTrashbin/trashbinRestore.feature:139
apiTrashbin/trashbinRestore.feature:211
apiTrashbin/trashbinRestore.feature:212
apiTrashbin/trashbinRestore.feature:255
apiTrashbin/trashbinRestore.feature:256
apiTrashbin/trashbinRestore.feature:257
apiTrashbin/trashbinRestore.feature:258
apiTrashbin/trashbinRestore.feature:259
apiTrashbin/trashbinRestore.feature:260
apiTrashbin/trashbinRestore.feature:275
apiTrashbin/trashbinRestore.feature:276
apiTrashbin/trashbinSharingToShares.feature:24
apiTrashbin/trashbinSharingToShares.feature:25
apiTrashbin/trashbinSharingToShares.feature:40
apiTrashbin/trashbinSharingToShares.feature:41
apiTrashbin/trashbinSharingToShares.feature:63
apiTrashbin/trashbinSharingToShares.feature:64
apiTrashbin/trashbinSharingToShares.feature:82
apiTrashbin/trashbinSharingToShares.feature:83
apiTrashbin/trashbinSharingToShares.feature:102
apiTrashbin/trashbinSharingToShares.feature:103
#
# https://github.com/owncloud/ocis-reva/issues/17 uploading with old-chunking does not work
# https://github.com/owncloud/ocis-reva/issues/56 remote.php/dav/uploads endpoint does not exist

114
ocis/tests/acceptance/expected-failures-on-OWNCLOUD-storage.txt
View File

@@ -1,7 +1,7 @@
# this file contains the scenarios from ownCloud10 core API tests that are currently expected to fail
# when run with OC storage
# when run with OWNCLOUD storage
#
# test scenarios that specifically fail with OC storage (that were tagged skipOnOcis-OC-Storage in core)
# test scenarios that specifically fail with OWNCLOUD storage (that were tagged skipOnOcis-OC-Storage in core)
#
apiWebdavProperties1/setFileProperties.feature:32
apiWebdavProperties1/setFileProperties.feature:33
@@ -381,10 +381,6 @@ apiShareManagementBasicToShares/deleteShareFromShares.feature:46
#
apiShareManagementBasicToShares/createShareToSharesFolder.feature:100
apiShareManagementBasicToShares/createShareToSharesFolder.feature:101
apiShareManagementBasicToShares/createShareToSharesFolder.feature:115
apiShareManagementBasicToShares/createShareToSharesFolder.feature:116
apiShareManagementBasicToShares/createShareToSharesFolder.feature:130
apiShareManagementBasicToShares/createShareToSharesFolder.feature:131
#
# https://github.com/owncloud/ocis-reva/issues/34 groups endpoint does not exist
#
@@ -909,78 +905,78 @@ apiTrashbin/trashbinFilesFolders.feature:44
apiTrashbin/trashbinFilesFolders.feature:45
apiTrashbin/trashbinFilesFolders.feature:60
apiTrashbin/trashbinFilesFolders.feature:61
apiTrashbin/trashbinFilesFolders.feature:135
apiTrashbin/trashbinFilesFolders.feature:136
#
# https://github.com/owncloud/core/issues/38006 Review and fix the tests that have sharing step to work with ocis
#
apiTrashbin/trashbinFilesFolders.feature:89
apiTrashbin/trashbinFilesFolders.feature:90
apiTrashbin/trashbinFilesFolders.feature:104
apiTrashbin/trashbinFilesFolders.feature:105
apiTrashbin/trashbinFilesFolders.feature:106
#
# https://github.com/owncloud/product/issues/273 invalid webdav responses for unauthorized requests.
#
apiTrashbin/trashbinFilesFolders.feature:184
apiTrashbin/trashbinFilesFolders.feature:185
apiTrashbin/trashbinFilesFolders.feature:202
apiTrashbin/trashbinFilesFolders.feature:203
apiTrashbin/trashbinFilesFolders.feature:226
apiTrashbin/trashbinFilesFolders.feature:227
apiTrashbin/trashbinFilesFolders.feature:240
apiTrashbin/trashbinFilesFolders.feature:241
apiTrashbin/trashbinFilesFolders.feature:254
apiTrashbin/trashbinFilesFolders.feature:255
apiTrashbin/trashbinFilesFolders.feature:154
apiTrashbin/trashbinFilesFolders.feature:155
apiTrashbin/trashbinFilesFolders.feature:172
apiTrashbin/trashbinFilesFolders.feature:173
apiTrashbin/trashbinFilesFolders.feature:196
apiTrashbin/trashbinFilesFolders.feature:197
apiTrashbin/trashbinFilesFolders.feature:210
apiTrashbin/trashbinFilesFolders.feature:211
apiTrashbin/trashbinFilesFolders.feature:224
apiTrashbin/trashbinFilesFolders.feature:225
#
# https://github.com/owncloud/product/issues/187
# Cannot create user with different username and emails
#
apiTrashbin/trashbinFilesFolders.feature:269
apiTrashbin/trashbinFilesFolders.feature:270
apiTrashbin/trashbinFilesFolders.feature:271
apiTrashbin/trashbinFilesFolders.feature:275
apiTrashbin/trashbinFilesFolders.feature:276
apiTrashbin/trashbinFilesFolders.feature:277
apiTrashbin/trashbinFilesFolders.feature:239
apiTrashbin/trashbinFilesFolders.feature:240
apiTrashbin/trashbinFilesFolders.feature:241
apiTrashbin/trashbinFilesFolders.feature:245
apiTrashbin/trashbinFilesFolders.feature:246
apiTrashbin/trashbinFilesFolders.feature:247
#
# https://github.com/owncloud/core/issues/38006 Review and fix the tests that have sharing step to work with ocis
#
apiTrashbin/trashbinRestore.feature:31
apiTrashbin/trashbinRestore.feature:32
apiTrashbin/trashbinRestore.feature:40
apiTrashbin/trashbinRestore.feature:41
#
# https://github.com/owncloud/ocis-reva/issues/117 cannot restore trashbin item
#
apiTrashbin/trashbinRestore.feature:62
apiTrashbin/trashbinRestore.feature:63
apiTrashbin/trashbinRestore.feature:76
apiTrashbin/trashbinRestore.feature:77
apiTrashbin/trashbinRestore.feature:54
apiTrashbin/trashbinRestore.feature:55
apiTrashbin/trashbinRestore.feature:70
apiTrashbin/trashbinRestore.feature:71
apiTrashbin/trashbinRestore.feature:90
apiTrashbin/trashbinRestore.feature:91
apiTrashbin/trashbinRestore.feature:92
apiTrashbin/trashbinRestore.feature:93
apiTrashbin/trashbinRestore.feature:112
apiTrashbin/trashbinRestore.feature:113
apiTrashbin/trashbinRestore.feature:114
apiTrashbin/trashbinRestore.feature:115
apiTrashbin/trashbinRestore.feature:116
apiTrashbin/trashbinRestore.feature:117
apiTrashbin/trashbinRestore.feature:140
apiTrashbin/trashbinRestore.feature:141
apiTrashbin/trashbinRestore.feature:142
apiTrashbin/trashbinRestore.feature:143
apiTrashbin/trashbinRestore.feature:160
apiTrashbin/trashbinRestore.feature:161
apiTrashbin/trashbinRestore.feature:179
apiTrashbin/trashbinRestore.feature:180
apiTrashbin/trashbinRestore.feature:197
apiTrashbin/trashbinRestore.feature:198
apiTrashbin/trashbinRestore.feature:270
apiTrashbin/trashbinRestore.feature:271
apiTrashbin/trashbinRestore.feature:314
apiTrashbin/trashbinRestore.feature:315
apiTrashbin/trashbinRestore.feature:316
apiTrashbin/trashbinRestore.feature:317
apiTrashbin/trashbinRestore.feature:318
apiTrashbin/trashbinRestore.feature:319
apiTrashbin/trashbinRestore.feature:334
apiTrashbin/trashbinRestore.feature:335
apiTrashbin/trashbinRestore.feature:94
apiTrashbin/trashbinRestore.feature:95
apiTrashbin/trashbinRestore.feature:118
apiTrashbin/trashbinRestore.feature:119
apiTrashbin/trashbinRestore.feature:120
apiTrashbin/trashbinRestore.feature:121
apiTrashbin/trashbinRestore.feature:138
apiTrashbin/trashbinRestore.feature:139
apiTrashbin/trashbinRestore.feature:211
apiTrashbin/trashbinRestore.feature:212
apiTrashbin/trashbinRestore.feature:255
apiTrashbin/trashbinRestore.feature:256
apiTrashbin/trashbinRestore.feature:257
apiTrashbin/trashbinRestore.feature:258
apiTrashbin/trashbinRestore.feature:259
apiTrashbin/trashbinRestore.feature:260
apiTrashbin/trashbinRestore.feature:275
apiTrashbin/trashbinRestore.feature:276
apiTrashbin/trashbinSharingToShares.feature:24
apiTrashbin/trashbinSharingToShares.feature:25
apiTrashbin/trashbinSharingToShares.feature:40
apiTrashbin/trashbinSharingToShares.feature:41
apiTrashbin/trashbinSharingToShares.feature:63
apiTrashbin/trashbinSharingToShares.feature:64
apiTrashbin/trashbinSharingToShares.feature:82
apiTrashbin/trashbinSharingToShares.feature:83
apiTrashbin/trashbinSharingToShares.feature:102
apiTrashbin/trashbinSharingToShares.feature:103
#
# https://github.com/owncloud/ocis-reva/issues/17 uploading with old-chunking does not work
# https://github.com/owncloud/ocis-reva/issues/56 remote.php/dav/uploads endpoint does not exist

24
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsDELETEAuth.feature
View File

@@ -22,37 +22,37 @@ Feature: auth
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/cloud/users/%username% |
| /ocs/v1.php/cloud/users/%username%/subadmins |
| endpoint |
| /ocs/v1.php/cloud/users/%username% |
| /ocs/v1.php/cloud/users/%username%/subadmins |
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"
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/v2.php/cloud/users/%username% |
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
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"
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/cloud/users/%username%/groups |
| endpoint |
| /ocs/v1.php/cloud/users/%username%/groups |
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 "996"
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/v2.php/cloud/users/%username%/groups |
| endpoint |
| /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "500"
And the OCS status code of responses on all endpoints should be "996"
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/v2.php/cloud/users/%username% |
| /ocs/v2.php/cloud/users/%username%/subadmins |
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
| /ocs/v2.php/cloud/users/%username%/subadmins |
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"

24
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsPOSTAuth.feature
View File

@@ -31,13 +31,13 @@ Feature: auth
# 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/cloud/users |
| 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 "400"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users |
| endpoint |
| /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "400"
@@ -45,13 +45,13 @@ Feature: auth
# 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/cloud/users/%username%/groups |
| endpoint |
| /ocs/v1.php/cloud/users/%username%/groups |
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 "400"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/groups |
| endpoint |
| /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "400"
@@ -59,12 +59,12 @@ Feature: auth
# 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/cloud/users/%username%/subadmins |
| endpoint |
| /ocs/v1.php/cloud/users/%username%/subadmins |
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 user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/subadmins |
| endpoint |
| /ocs/v2.php/cloud/users/%username%/subadmins |
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"

20
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsPUTAuth.feature
View File

@@ -17,13 +17,13 @@ Feature: auth
# 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% |
| endpoint |
| /ocs/v1.php/cloud/users/%username% |
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 "103"
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "103"
@@ -32,15 +32,15 @@ Feature: auth
# 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%/disable |
| /ocs/v1.php/cloud/users/%username%/enable |
| endpoint |
| /ocs/v1.php/cloud/users/%username%/disable |
| /ocs/v1.php/cloud/users/%username%/enable |
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 administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/disable |
| /ocs/v2.php/cloud/users/%username%/enable |
| endpoint |
| /ocs/v2.php/cloud/users/%username%/disable |
| /ocs/v2.php/cloud/users/%username%/enable |
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"

14
ocis/tests/acceptance/features/apiOcisSpecific/apiShareCreateSpecial2-createShareWithInvalidPermissions.feature
View File

@@ -21,8 +21,8 @@ Feature: cannot share resources with invalid permissions
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 |
| 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
@@ -38,8 +38,8 @@ Feature: cannot share resources with invalid permissions
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 |
| 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 |

24
ocis/tests/acceptance/features/apiOcisSpecific/apiShareManagementBasic-createShare.feature
View File

@@ -53,8 +53,8 @@ Feature: sharing
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 |
| 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
@@ -66,16 +66,16 @@ Feature: sharing
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 |
| 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:

13
ocis/tests/acceptance/features/apiOcisSpecific/apiShareOperations-gettingShares.feature
View File

@@ -2,14 +2,15 @@
Feature: sharing
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And user "Brian" has been created with default attributes and without skeleton files
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 user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
And using OCS API version "<ocs_api_version>"
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
@@ -24,9 +25,7 @@ Feature: sharing
@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 user "Alice" has created folder "/PARENT"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
And using OCS API version "<ocs_api_version>"
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>"

2
ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink1-createPublicLinkShare.feature
View File

@@ -23,7 +23,7 @@ Feature: create a public link share
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 |
| 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

3
ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-updatePublicLinkShare.feature
View File

@@ -3,8 +3,7 @@ Feature: update a public link share
Background:
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has created folder "/FOLDER"
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

3
ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-uploadToPublicLinkShare.feature
View File

@@ -3,8 +3,7 @@
Feature: upload to a public link share
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And user "Alice" has created folder "/FOLDER"
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

30
ocis/tests/acceptance/features/apiOcisSpecific/apiShareUpdate-updateShare.feature
View File

@@ -5,7 +5,7 @@ Feature: sharing
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@skipOnOcis-EOS-Storage @toFixOnOCIS @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
@skipOnOcis-EOS-Storage @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Share ownership change after moving a shared file to another share
Given these users have been created with default attributes and without skeleton files:
@@ -43,7 +43,7 @@ Feature: sharing
And as "Alice" folder "/Alice-folder/folder2" should exist
And as "Carol" folder "/Carol-folder/folder2" should not exist
@skipOnOcis-OC-Storage @toFixOnOCIS @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
@skipOnOcis-OC-Storage @issue-ocis-reva-243 @skipOnOcis-OCIS-Storage
# same as oC10 core Scenario but without displayname_owner because EOS does not report it
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: Share ownership change after moving a shared file to another share
@@ -59,22 +59,22 @@ Feature: sharing
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 |
| 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-350 @issue-ocis-reva-352 @issue-37653
@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>"

1
ocis/tests/acceptance/features/apiOcisSpecific/apiTrashbin-trashbinDelete.feature
View File

@@ -19,7 +19,6 @@ Feature: files and folders can be deleted from the trashbin
@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

2
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove1-moveFolderToBlacklistedName.feature
View File

@@ -8,7 +8,7 @@ Feature: users cannot move (rename) a folder to a blacklisted name
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@issue-ocis-reva-211 @skipOnOcis-EOS-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-269
@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

8
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFile.feature
View File

@@ -7,13 +7,13 @@ Feature: move (rename) file
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 welcome data" to "/welcome.txt"
And user "Alice" has uploaded file with content "text file 0" to "/textfile0.txt"
@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
When user "Alice" moves file "/textfile0.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:
@@ -25,9 +25,9 @@ Feature: move (rename) file
# 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
When user "Alice" moves file "/textfile0.txt" to "/textfile0.part" using the WebDAV API
Then the HTTP status code should be "201"
And as "Alice" file "/welcome.part" should exist
And as "Alice" file "/textfile0.part" should exist
Examples:
| dav_version |
| old |

4
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavMove2-moveFileToBlacklistedName.feature
View File

@@ -7,13 +7,13 @@ Feature: users cannot move (rename) a file to a blacklisted name
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 welcome data" to "/welcome.txt"
And user "Alice" has uploaded file with content "text file 0" to "/textfile0.txt"
@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
When user "Alice" moves file "/textfile0.txt" to "/.htaccess" using the WebDAV API
Then the HTTP status code should be "201"
And as "Alice" file "/.htaccess" should exist
Examples:

2
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties1-setFileProperties.feature
View File

@@ -8,7 +8,7 @@ Feature: set file properties
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-276
@skipOnOcis-OC-Storage @issue-ocis-reva-276 @skipOnOcis-OCIS-Storage
# 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

42
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavProperties2-getFileProperties.feature
View File

@@ -17,10 +17,10 @@ Feature: get file properties
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 |
| 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 |
@@ -45,11 +45,11 @@ Feature: get file properties
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 |
| dav_version | file_name |
| old | /file ?2.txt |
| new | /file ?2.txt |
@issue-ocis-reva-214 @skipOnOcis-OCIS-Storage @issue-ocis-reva-471
@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 folder names
Given using <dav_version> DAV path
@@ -61,21 +61,21 @@ Feature: get file properties
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 |
| 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 | /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
@issue-ocis-reva-214 @skipOnOcis-EOS-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
# 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
@@ -87,11 +87,11 @@ Feature: get file properties
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 |
| 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
@skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Do a PROPFIND of various folder names
Given using <dav_version> DAV path

10
ocis/tests/acceptance/features/apiOcisSpecific/apiWebdavUpload1-uploadFile.feature
View File

@@ -8,18 +8,18 @@ Feature: upload file
Given using OCS API version "1"
And user "Alice" has been created with default attributes and without skeleton files
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-ocis-reva-265
@skipOnOcis-OC-Storage @issue-ocis-reva-265 @skipOnOcis-OCIS-Storage
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: upload a file 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" |
| dav_version | file_name |
| old | "file ?2.txt" |
| new | "file ?2.txt" |
@skipOnOcis-OC-Storage @skipOnOcis-OCIS-Storage @issue-product-127
@skipOnOcis-OC-Storage @issue-product-127 @skipOnOcis-OCIS-Storage
# 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