diff --git a/tests/acceptance/expected-failures-API-on-OCIS-storage.md b/tests/acceptance/expected-failures-API-on-OCIS-storage.md index 6afa75ee0c2..2badd4814c1 100644 --- a/tests/acceptance/expected-failures-API-on-OCIS-storage.md +++ b/tests/acceptance/expected-failures-API-on-OCIS-storage.md @@ -35,17 +35,17 @@ _ocdav: double-check the webdav property parsing when custom namespaces are used #### [file versions do not report the version author](https://github.com/owncloud/ocis/issues/2914) -- [coreApiVersions/fileVersionAuthor.feature:12](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L12) -- [coreApiVersions/fileVersionAuthor.feature:43](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L43) -- [coreApiVersions/fileVersionAuthor.feature:70](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L70) -- [coreApiVersions/fileVersionAuthor.feature:96](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L96) -- [coreApiVersions/fileVersionAuthor.feature:129](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L129) -- [coreApiVersions/fileVersionAuthor.feature:156](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L156) -- [coreApiVersions/fileVersionAuthor.feature:187](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L187) -- [coreApiVersions/fileVersionAuthor.feature:222](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L222) -- [coreApiVersions/fileVersionAuthor.feature:274](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L274) -- [coreApiVersions/fileVersionAuthor.feature:323](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L323) -- [coreApiVersions/fileVersionAuthor.feature:344](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L344) +- [coreApiVersions/fileVersionAuthor.feature:15](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L15) +- [coreApiVersions/fileVersionAuthor.feature:46](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L46) +- [coreApiVersions/fileVersionAuthor.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L73) +- [coreApiVersions/fileVersionAuthor.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L99) +- [coreApiVersions/fileVersionAuthor.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L132) +- [coreApiVersions/fileVersionAuthor.feature:159](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L159) +- [coreApiVersions/fileVersionAuthor.feature:190](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L190) +- [coreApiVersions/fileVersionAuthor.feature:225](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L225) +- [coreApiVersions/fileVersionAuthor.feature:277](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L277) +- [coreApiVersions/fileVersionAuthor.feature:326](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L326) +- [coreApiVersions/fileVersionAuthor.feature:347](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L347) ### Sync @@ -58,98 +58,98 @@ Synchronization features like etag propagation, setting mtime and locking files #### [Webdav LOCK operations](https://github.com/owncloud/ocis/issues/1284) -- [coreApiWebdavLocks/exclusiveLocks.feature:46](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L46) -- [coreApiWebdavLocks/exclusiveLocks.feature:47](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L47) -- [coreApiWebdavLocks/exclusiveLocks.feature:48](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L48) - [coreApiWebdavLocks/exclusiveLocks.feature:49](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L49) -- [coreApiWebdavLocks/exclusiveLocks.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L54) -- [coreApiWebdavLocks/exclusiveLocks.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L55) -- [coreApiWebdavLocks/exclusiveLocks.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L73) -- [coreApiWebdavLocks/exclusiveLocks.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L74) -- [coreApiWebdavLocks/exclusiveLocks.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L75) +- [coreApiWebdavLocks/exclusiveLocks.feature:50](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L50) +- [coreApiWebdavLocks/exclusiveLocks.feature:51](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L51) +- [coreApiWebdavLocks/exclusiveLocks.feature:52](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L52) +- [coreApiWebdavLocks/exclusiveLocks.feature:57](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L57) +- [coreApiWebdavLocks/exclusiveLocks.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L58) - [coreApiWebdavLocks/exclusiveLocks.feature:76](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L76) -- [coreApiWebdavLocks/exclusiveLocks.feature:81](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L81) -- [coreApiWebdavLocks/exclusiveLocks.feature:82](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L82) -- [coreApiWebdavLocks/exclusiveLocks.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L100) -- [coreApiWebdavLocks/exclusiveLocks.feature:101](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L101) -- [coreApiWebdavLocks/exclusiveLocks.feature:102](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L102) +- [coreApiWebdavLocks/exclusiveLocks.feature:77](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L77) +- [coreApiWebdavLocks/exclusiveLocks.feature:78](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L78) +- [coreApiWebdavLocks/exclusiveLocks.feature:79](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L79) +- [coreApiWebdavLocks/exclusiveLocks.feature:84](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L84) +- [coreApiWebdavLocks/exclusiveLocks.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L85) - [coreApiWebdavLocks/exclusiveLocks.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L103) -- [coreApiWebdavLocks/exclusiveLocks.feature:108](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L108) -- [coreApiWebdavLocks/exclusiveLocks.feature:109](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L109) -- [coreApiWebdavLocks/requestsWithToken.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L29) -- [coreApiWebdavLocks/requestsWithToken.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L30) -- [coreApiWebdavLocks/requestsWithToken.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L35) -- [coreApiWebdavLocks2/independentLocks.feature:23](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L23) -- [coreApiWebdavLocks2/independentLocks.feature:24](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L24) +- [coreApiWebdavLocks/exclusiveLocks.feature:104](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L104) +- [coreApiWebdavLocks/exclusiveLocks.feature:105](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L105) +- [coreApiWebdavLocks/exclusiveLocks.feature:106](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L106) +- [coreApiWebdavLocks/exclusiveLocks.feature:111](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L111) +- [coreApiWebdavLocks/exclusiveLocks.feature:112](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L112) +- [coreApiWebdavLocks/requestsWithToken.feature:32](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L32) +- [coreApiWebdavLocks/requestsWithToken.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L33) +- [coreApiWebdavLocks/requestsWithToken.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L38) - [coreApiWebdavLocks2/independentLocks.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L25) - [coreApiWebdavLocks2/independentLocks.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L26) -- [coreApiWebdavLocks2/independentLocks.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L31) -- [coreApiWebdavLocks2/independentLocks.feature:32](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L32) -- [coreApiWebdavLocks2/independentLocks.feature:51](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L51) -- [coreApiWebdavLocks2/independentLocks.feature:52](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L52) +- [coreApiWebdavLocks2/independentLocks.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L27) +- [coreApiWebdavLocks2/independentLocks.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L28) +- [coreApiWebdavLocks2/independentLocks.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L33) +- [coreApiWebdavLocks2/independentLocks.feature:34](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L34) - [coreApiWebdavLocks2/independentLocks.feature:53](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L53) - [coreApiWebdavLocks2/independentLocks.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L54) - [coreApiWebdavLocks2/independentLocks.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L55) - [coreApiWebdavLocks2/independentLocks.feature:56](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L56) - [coreApiWebdavLocks2/independentLocks.feature:57](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L57) - [coreApiWebdavLocks2/independentLocks.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L58) -- [coreApiWebdavLocks2/independentLocks.feature:63](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L63) -- [coreApiWebdavLocks2/independentLocks.feature:64](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L64) +- [coreApiWebdavLocks2/independentLocks.feature:59](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L59) +- [coreApiWebdavLocks2/independentLocks.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L60) - [coreApiWebdavLocks2/independentLocks.feature:65](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L65) - [coreApiWebdavLocks2/independentLocks.feature:66](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L66) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L28) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L29) +- [coreApiWebdavLocks2/independentLocks.feature:67](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L67) +- [coreApiWebdavLocks2/independentLocks.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L68) - [coreApiWebdavLocks2/independentLocksShareToShares.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L30) - [coreApiWebdavLocks2/independentLocksShareToShares.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L31) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:36](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L36) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:37](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L37) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:57](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L57) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L58) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:32](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L32) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L33) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L38) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:39](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L39) - [coreApiWebdavLocks2/independentLocksShareToShares.feature:59](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L59) - [coreApiWebdavLocks2/independentLocksShareToShares.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L60) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:65](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L65) -- [coreApiWebdavLocks2/independentLocksShareToShares.feature:66](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L66) -- [coreApiWebdavLocksUnlock/unlock.feature:20](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L20) -- [coreApiWebdavLocksUnlock/unlock.feature:21](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L21) -- [coreApiWebdavLocksUnlock/unlock.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L26) -- [coreApiWebdavLocksUnlock/unlock.feature:40](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L40) -- [coreApiWebdavLocksUnlock/unlock.feature:41](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L41) -- [coreApiWebdavLocksUnlock/unlock.feature:63](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L63) -- [coreApiWebdavLocksUnlock/unlock.feature:64](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L64) -- [coreApiWebdavLocksUnlock/unlock.feature:65](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L65) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L61) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:62](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L62) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:67](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L67) +- [coreApiWebdavLocks2/independentLocksShareToShares.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L68) +- [coreApiWebdavLocksUnlock/unlock.feature:23](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L23) +- [coreApiWebdavLocksUnlock/unlock.feature:24](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L24) +- [coreApiWebdavLocksUnlock/unlock.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L29) +- [coreApiWebdavLocksUnlock/unlock.feature:43](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L43) +- [coreApiWebdavLocksUnlock/unlock.feature:44](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L44) - [coreApiWebdavLocksUnlock/unlock.feature:66](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L66) -- [coreApiWebdavLocksUnlock/unlock.feature:71](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L71) -- [coreApiWebdavLocksUnlock/unlock.feature:72](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L72) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L25) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L26) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L27) +- [coreApiWebdavLocksUnlock/unlock.feature:67](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L67) +- [coreApiWebdavLocksUnlock/unlock.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L68) +- [coreApiWebdavLocksUnlock/unlock.feature:69](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L69) +- [coreApiWebdavLocksUnlock/unlock.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L74) +- [coreApiWebdavLocksUnlock/unlock.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L75) - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L28) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L33) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:34](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L34) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:49](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L49) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:50](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L50) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:51](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L51) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L29) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L30) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L31) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:36](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L36) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:37](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L37) - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:52](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L52) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:57](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L57) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L58) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L73) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L74) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L75) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:53](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L53) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L54) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L55) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L60) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L61) - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:76](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L76) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:81](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L81) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:82](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L82) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:97](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L97) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:98](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L98) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L99) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:77](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L77) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:78](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L78) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:79](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L79) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:84](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L84) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L85) - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L100) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:105](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L105) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:106](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L106) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:121](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L121) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:122](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L122) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L123) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:101](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L101) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:102](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L102) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L103) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:108](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L108) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:109](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L109) - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:124](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L124) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:129](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L129) -- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:130](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L130) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L125) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:126](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L126) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:127](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L127) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L132) +- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:133](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L133) ### Share @@ -243,21 +243,21 @@ cannot share a folder with create permission #### [deleting a file inside a received shared folder is moved to the trash-bin of the sharer not the receiver](https://github.com/owncloud/ocis/issues/1124) -- [coreApiTrashbin/trashbinSharingToShares.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L27) -- [coreApiTrashbin/trashbinSharingToShares.feature:44](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L44) -- [coreApiTrashbin/trashbinSharingToShares.feature:49](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L49) -- [coreApiTrashbin/trashbinSharingToShares.feature:71](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L71) -- [coreApiTrashbin/trashbinSharingToShares.feature:76](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L76) -- [coreApiTrashbin/trashbinSharingToShares.feature:98](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L98) -- [coreApiTrashbin/trashbinSharingToShares.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L103) -- [coreApiTrashbin/trashbinSharingToShares.feature:126](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L126) -- [coreApiTrashbin/trashbinSharingToShares.feature:131](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L131) -- [coreApiTrashbin/trashbinSharingToShares.feature:154](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L154) -- [coreApiTrashbin/trashbinSharingToShares.feature:159](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L159) -- [coreApiTrashbin/trashbinSharingToShares.feature:182](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L182) -- [coreApiTrashbin/trashbinSharingToShares.feature:187](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L187) -- [coreApiTrashbin/trashbinSharingToShares.feature:210](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L210) -- [coreApiTrashbin/trashbinSharingToShares.feature:234](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L234) +- [coreApiTrashbin/trashbinSharingToShares.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L30) +- [coreApiTrashbin/trashbinSharingToShares.feature:47](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L47) +- [coreApiTrashbin/trashbinSharingToShares.feature:52](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L52) +- [coreApiTrashbin/trashbinSharingToShares.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L74) +- [coreApiTrashbin/trashbinSharingToShares.feature:79](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L79) +- [coreApiTrashbin/trashbinSharingToShares.feature:101](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L101) +- [coreApiTrashbin/trashbinSharingToShares.feature:106](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L106) +- [coreApiTrashbin/trashbinSharingToShares.feature:129](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L129) +- [coreApiTrashbin/trashbinSharingToShares.feature:134](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L134) +- [coreApiTrashbin/trashbinSharingToShares.feature:157](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L157) +- [coreApiTrashbin/trashbinSharingToShares.feature:162](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L162) +- [coreApiTrashbin/trashbinSharingToShares.feature:185](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L185) +- [coreApiTrashbin/trashbinSharingToShares.feature:190](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L190) +- [coreApiTrashbin/trashbinSharingToShares.feature:213](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L213) +- [coreApiTrashbin/trashbinSharingToShares.feature:237](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L237) #### [changing user quota gives ocs status 103 / Cannot set quota](https://github.com/owncloud/product/issues/247) diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature b/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature index 859630a151a..1fa366193a4 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinDelete.feature @@ -14,7 +14,7 @@ Feature: files and folders can be deleted from the trashbin And user "Alice" has uploaded file with content "to delete" to "/PARENT/CHILD/child.txt" @smokeTest - Scenario Outline: Trashbin can be emptied + Scenario Outline: trashbin can be emptied Given using DAV path And 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" @@ -85,7 +85,7 @@ Feature: files and folders can be deleted from the trashbin | spaces | - Scenario Outline: User tries to delete another user's trashbin + Scenario Outline: user tries to delete another user's trashbin Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has deleted file "/textfile0.txt" @@ -105,7 +105,7 @@ Feature: files and folders can be deleted from the trashbin | spaces | 404 | - Scenario Outline: User tries to delete trashbin file using invalid password + Scenario Outline: user tries to delete trashbin file using invalid password Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has deleted file "/textfile0.txt" @@ -128,7 +128,7 @@ Feature: files and folders can be deleted from the trashbin | spaces | - Scenario Outline: User tries to delete trashbin file using no password + Scenario Outline: user tries to delete trashbin file using no password Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has deleted file "/textfile0.txt" diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature b/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature index cf9749e811b..98b79afb590 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinFilesFolders.feature @@ -159,7 +159,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | @issue-3561 - Scenario Outline: Listing other user's trashbin is prohibited + Scenario Outline: listing other user's trashbin is prohibited Given using DAV path And user "testtrashbin100" has been created with default attributes and without skeleton files And user "testtrashbin100" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt" @@ -177,7 +177,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | 404 | @issue-3561 @smokeTest - Scenario Outline: Listing other user's trashbin is prohibited with multiple files on trashbin + Scenario Outline: listing other user's trashbin is prohibited with multiple files on trashbin Given using DAV path And user "testtrashbin101" has been created with default attributes and without skeleton files And user "testtrashbin101" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -198,7 +198,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | 404 | @issue-3561 @provisioning_api-app-required - Scenario Outline: Listing other user's trashbin is prohibited for newly recreated user with same name + Scenario Outline: listing other user's trashbin is prohibited for newly recreated user with same name Given using DAV path And user "testtrashbin102" has been created with default attributes and without skeleton files And user "testtrashbin102" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" @@ -224,7 +224,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | 404 | @issue-3561 - Scenario Outline: Listing other user's empty unused trashbin is prohibited + Scenario Outline: listing other user's empty unused trashbin is prohibited Given using DAV path And user "testtrashbinempty" has been created with default attributes and without skeleton files And user "testtrashbinempty" has uploaded file "filesForUpload/textfile.txt" to "/textfile1.txt" @@ -240,7 +240,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | @issue-3561 - Scenario Outline: Listing non-existent user's trashbin is prohibited + Scenario Outline: listing non-existent user's trashbin is prohibited Given using DAV path When user "Alice" tries to list the trashbin content for user "testtrashbinnotauser" Then the HTTP status code should be "404" @@ -254,7 +254,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | @smokeTest - Scenario Outline: Get trashbin content with wrong password + Scenario Outline: get trashbin content with wrong password Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has deleted file "/textfile0.txt" @@ -273,7 +273,7 @@ Feature: files and folders exist in the trashbin after being deleted | spaces | @smokeTest - Scenario Outline: Get trashbin content without password + Scenario Outline: get trashbin content without password Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt" And user "Alice" has deleted file "/textfile0.txt" diff --git a/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature b/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature index 6536df18934..e3ca1484c06 100644 --- a/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature +++ b/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature @@ -1,5 +1,8 @@ @api Feature: using trashbin together with sharing + As a user + I want the deletion of the resources that I shared to end up in my trashbin + So that I can restore the resources that were accidentally deleted Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature b/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature index b8209ddcfaf..9c8b7e10e20 100644 --- a/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature +++ b/tests/acceptance/features/coreApiTrashbinRestore/trashbinRestore.feature @@ -1,5 +1,5 @@ @api @issue-1324 -Feature: Restore deleted files/folders +Feature: restore deleted files/folders As a user I would like to restore files/folders So that I can recover accidentally deleted files/folders in ownCloud @@ -9,7 +9,7 @@ Feature: Restore deleted files/folders And user "Alice" has uploaded file with content "file to delete" to "/textfile0.txt" @smokeTest - Scenario Outline: A deleted file can be restored + Scenario Outline: deleted file can be restored Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has created folder "/PARENT" @@ -35,7 +35,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A file deleted from a folder can be restored to the original folder + Scenario Outline: file deleted from a folder can be restored to the original folder Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has moved file "/textfile0.txt" to "/new-folder/new-file.txt" @@ -51,7 +51,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A file deleted from a folder is restored to the original folder if the original folder was deleted and restored + Scenario Outline: file deleted from a folder is restored to the original folder if the original folder was deleted and restored Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has moved file "/textfile0.txt" to "/new-folder/new-file.txt" @@ -69,7 +69,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: a file is deleted and restored to a new destination + Scenario Outline: file is deleted and restored to a new destination Given using DAV path And user "Alice" has created folder "/PARENT" And user "Alice" has created folder "/PARENT/CHILD" @@ -111,7 +111,7 @@ Feature: Restore deleted files/folders | new | "/PARENT/.hiddenfile0.txt" | ".hiddenfile0.txt" | - Scenario Outline: A file deleted from a folder is restored to the original folder if the original folder was deleted and recreated + Scenario Outline: file deleted from a folder is restored to the original folder if the original folder was deleted and recreated Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has moved file "/textfile0.txt" to "/new-folder/new-file.txt" @@ -131,7 +131,7 @@ Feature: Restore deleted files/folders | new | @smokeTest - Scenario Outline: A deleted file cannot be restored by a different user + Scenario Outline: deleted file cannot be restored by a different user Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has deleted file "/textfile0.txt" @@ -146,7 +146,7 @@ Feature: Restore deleted files/folders | new | 404 | @smokeTest - Scenario Outline: A deleted file cannot be restored with invalid password + Scenario Outline: deleted file cannot be restored with invalid password Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has deleted file "/textfile0.txt" @@ -161,7 +161,7 @@ Feature: Restore deleted files/folders | new | @smokeTest - Scenario Outline: A deleted file cannot be restored without using a password + Scenario Outline: deleted file cannot be restored without using a password Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has deleted file "/textfile0.txt" @@ -176,7 +176,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: Files with strange names can be restored + Scenario Outline: files with strange names can be restored Given using DAV path And user "Alice" has uploaded file with content "file original content" to "" And user "Alice" has deleted file "" @@ -195,7 +195,7 @@ Feature: Restore deleted files/folders | new | sample,1.txt | - Scenario Outline: A file deleted from a multi level sub-folder can be restored to the original folder + Scenario Outline: file deleted from a multi level sub-folder can be restored to the original folder Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has created folder "/new-folder/folder1/" @@ -213,7 +213,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted multi level folder can be restored including the content + Scenario Outline: deleted multi level folder can be restored including the content Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has created folder "/new-folder/folder1/" @@ -231,7 +231,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A subfolder from a deleted multi level folder can be restored including the content + Scenario Outline: subfolder from a deleted multi level folder can be restored including the content Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has created folder "/new-folder/folder1" @@ -251,7 +251,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A file from a deleted multi level sub-folder can be restored + Scenario Outline: file from a deleted multi level sub-folder can be restored Given using DAV path And user "Alice" has created folder "/new-folder" And user "Alice" has created folder "/new-folder/folder1/" @@ -271,7 +271,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted hidden file can be restored + Scenario Outline: deleted hidden file can be restored Given using DAV path And user "Alice" has created folder "/FOLDER" And user "Alice" has uploaded the following files with content "hidden file" @@ -383,7 +383,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted file inside a nested folder can be restored to a different location + Scenario Outline: deleted file inside a nested folder can be restored to a different location Given using DAV path And user "Alice" has created folder "/parent_folder" And user "Alice" has created folder "/parent_folder/sub" @@ -401,7 +401,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted file inside a nested folder cannot be restored to the original location if the location doesn't exist + Scenario Outline: deleted file inside a nested folder cannot be restored to the original location if the location doesn't exist Given using DAV path And user "Alice" has created folder "/parent_folder" And user "Alice" has created folder "/parent_folder/sub" @@ -420,7 +420,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted file inside a nested folder can be restored to the original location if the location exists + Scenario Outline: deleted file inside a nested folder can be restored to the original location if the location exists Given using DAV path And user "Alice" has created folder "/parent_folder" And user "Alice" has created folder "/parent_folder/sub" @@ -444,7 +444,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted file inside a nested folder cannot be restored without the destination + Scenario Outline: deleted file inside a nested folder cannot be restored without the destination Given using DAV path And user "Alice" has created folder "/parent_folder" And user "Alice" has created folder "/parent_folder/sub" @@ -463,7 +463,7 @@ Feature: Restore deleted files/folders | new | - Scenario Outline: A deleted file cannot be restored without the destination + Scenario Outline: deleted file cannot be restored without the destination Given using DAV path And user "Alice" has uploaded file with content "parent text" to "/parent.txt" And user "Alice" has deleted file "parent.txt" diff --git a/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature b/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature index 0e013e40164..a5cab861f61 100644 --- a/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature +++ b/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature @@ -1,5 +1,8 @@ @api @issue-2914 Feature: file versions remember the author of each version + As a user + I want to know the author of each version of a file + So that I can better understand the version history and choose a version to restore Background: Given using OCS API version "2" diff --git a/tests/acceptance/features/coreApiVersions/fileVersions.feature b/tests/acceptance/features/coreApiVersions/fileVersions.feature index 98e3f4bdd93..07f4aa9e1aa 100644 --- a/tests/acceptance/features/coreApiVersions/fileVersions.feature +++ b/tests/acceptance/features/coreApiVersions/fileVersions.feature @@ -1,6 +1,8 @@ @api - Feature: dav-versions + As a user + I want the versions of files to be available + So that I can manage the changes made to the files Background: Given using OCS API version "2" @@ -8,13 +10,13 @@ Feature: dav-versions And user "Alice" has been created with default attributes and without skeleton files - Scenario: Upload file and no version is available + Scenario: upload file and no version is available When user "Alice" uploads file "filesForUpload/davtest.txt" to "/davtest.txt" using the WebDAV API Then the HTTP status code should be "201" And the version folder of file "/davtest.txt" for user "Alice" should contain "0" elements - Scenario: Upload file and no version is available using various chunking methods (except new chunking) + Scenario: upload file and no version is available using various chunking methods (except new chunking) When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code should be "200" And the version folder of file "/davtest.txt-olddav-regular" for user "Alice" should contain "0" elements @@ -22,7 +24,7 @@ Feature: dav-versions And the version folder of file "/davtest.txt-olddav-oldchunking" for user "Alice" should contain "0" elements @smokeTest - Scenario: Upload a file twice and versions are available + Scenario: upload a file twice and versions are available When user "Alice" uploads file "filesForUpload/davtest.txt" to "/davtest.txt" using the WebDAV API And user "Alice" uploads file "filesForUpload/davtest.txt" to "/davtest.txt" using the WebDAV API Then the HTTP status code of responses on each endpoint should be "201, 204" respectively @@ -30,7 +32,7 @@ Feature: dav-versions And the content length of file "/davtest.txt" with version index "1" for user "Alice" in versions folder should be "8" - Scenario: Upload a file twice and versions are available using various chunking methods (except new chunking) + Scenario: upload a file twice and versions are available using various chunking methods (except new chunking) When user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms except new chunking using the WebDAV API And user "Alice" uploads file "filesForUpload/davtest.txt" to filenames based on "/davtest.txt" with all mechanisms except new chunking using the WebDAV API Then the HTTP status code of responses on all endpoints should be "200" @@ -39,7 +41,7 @@ Feature: dav-versions And the version folder of file "/davtest.txt-olddav-oldchunking" for user "Alice" should contain "1" element @smokeTest - Scenario: Remove a file + Scenario: remove a file Given user "Alice" has uploaded file "filesForUpload/davtest.txt" to "/davtest.txt" And user "Alice" has uploaded file "filesForUpload/davtest.txt" to "/davtest.txt" And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element @@ -49,7 +51,7 @@ Feature: dav-versions And the version folder of file "/davtest.txt" for user "Alice" should contain "0" elements @smokeTest - Scenario: Restore a file and check, if the content is now in the current file + Scenario: restore a file and check its content Given user "Alice" has uploaded file with content "Test Content." to "/davtest.txt" And user "Alice" has uploaded file with content "Content Test Updated." to "/davtest.txt" And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element @@ -58,7 +60,7 @@ Feature: dav-versions And the content of file "/davtest.txt" for user "Alice" should be "Test Content." @smokeTest @skipOnStorage:ceph @skipOnStorage:scality - Scenario: Restore a file back to bigger content and check, if the content is now in the current file + Scenario: restore a file back to bigger content and check its content Given user "Alice" has uploaded file with content "Back To The Future." to "/davtest.txt" And user "Alice" has uploaded file with content "Update Content." to "/davtest.txt" And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element @@ -67,7 +69,7 @@ Feature: dav-versions And the content of file "/davtest.txt" for user "Alice" should be "Back To The Future." @smokeTest @skipOnStorage:ceph - Scenario Outline: Uploading a chunked file does create the correct version that can be restored + Scenario Outline: uploading a chunked file does create the correct version that can be restored Given using DAV path And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt" When user "Alice" uploads file "filesForUpload/davtest.txt" to "/textfile0.txt" in 2 chunks using the WebDAV API @@ -83,7 +85,7 @@ Feature: dav-versions | old | 201 | @skipOnStorage:ceph @skipOnStorage:scality - Scenario: Restore a file and check, if the content and correct checksum is now in the current file + Scenario: restore a file and check the content and checksum Given user "Alice" has uploaded file with content "AAAAABBBBBCCCCC" and checksum "MD5:45a72715acdd5019c5be30bdbb75233e" to "/davtest.txt" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/davtest.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a" And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element @@ -93,7 +95,7 @@ Feature: dav-versions And as user "Alice" the webdav checksum of "/davtest.txt" via propfind should match "SHA1:acfa6b1565f9710d4d497c6035d5c069bd35a8e8 MD5:45a72715acdd5019c5be30bdbb75233e ADLER32:1ecd03df" - Scenario: User cannot access meta folder of a file which is owned by somebody else + Scenario: user cannot access meta folder of a file which is owned by somebody else Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "123" to "/davtest.txt" And we save it into "FILEID" @@ -101,13 +103,13 @@ Feature: dav-versions Then the HTTP status code should be "400" or "404" - Scenario: User cannot access meta folder of a file which does not exist + Scenario: user cannot access meta folder of a file which does not exist Given user "Brian" has been created with default attributes and without skeleton files When user "Brian" sends HTTP method "PROPFIND" to URL "/remote.php/dav/meta/MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU2OjhjY2QyNzUxLTkwYTQtNDBmMi1iOWYzLTYxZWRmODQ0MjFmNA==" Then the HTTP status code should be "400" or "404" - Scenario Outline: User cannot access meta folder of a file with invalid fileid + Scenario Outline: user cannot access meta folder of a file with invalid fileid Given user "Brian" has been created with default attributes and without skeleton files When user "Brian" sends HTTP method "PROPFIND" to URL "/remote.php/dav/meta//v" Then the HTTP status code should be "400" or "404" @@ -119,7 +121,7 @@ Feature: dav-versions | MTI4NGQyMzgtYWE5Mi00MmNlLWJkxzQtMGIwMDAwMDA5MTU2OjhjY2QyNzUxLTkwYTQtNDBmMi1iOWYzLTYxZWRmODQ0MjFmNA== | 1284d238-aa92-42ce-bd�4-0b0000009156:8ccd2751-90a4-40f2-b9f3-61edf84421f4 | with : and � sign | - Scenario: the version history is preserved when a file is renamed + Scenario: version history is preserved when a file is renamed Given user "Alice" has uploaded file with content "old content" to "/textfile.txt" And user "Alice" has uploaded file with content "new content" to "/textfile.txt" And user "Alice" has moved file "/textfile.txt" to "/renamedfile.txt" @@ -128,7 +130,7 @@ Feature: dav-versions And the content of file "/renamedfile.txt" for user "Alice" should be "old content" - Scenario: User can access version number after moving a file + Scenario: user can access version number after moving a file Given user "Alice" has created folder "testFolder" And user "Alice" has uploaded file with content "uploaded content" to "textfile0.txt" And user "Alice" has uploaded file with content "version 1" to "textfile0.txt" @@ -140,14 +142,14 @@ Feature: dav-versions And the number of versions should be "3" - Scenario: Original file has version number 0 + Scenario: original file has version number 0 Given user "Alice" has uploaded file with content "uploaded content" to "textfile0.txt" When user "Alice" gets the number of versions of file "textfile0.txt" Then the HTTP status code should be "207" And the number of versions should be "0" - Scenario: the number of etag elements in response changes according to version of the file + Scenario: number of etag elements in response changes according to version of the file Given user "Alice" has uploaded file with content "uploaded content" 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" @@ -194,20 +196,20 @@ Feature: dav-versions And the downloaded content should be "uploaded content" - Scenario: User can retrieve meta information of a root folder + Scenario: user can retrieve meta information of a root folder When user "Alice" retrieves the meta information of file "/" using the meta API Then the HTTP status code should be "207" And the single response should contain a property "oc:meta-path-for-user" with value "/" - Scenario: User can retrieve meta information of a file + Scenario: user can retrieve meta information of a file Given user "Alice" has uploaded file with content "123" to "/davtest.txt" When user "Alice" retrieves the meta information of file "/davtest.txt" using the meta API Then the HTTP status code should be "207" And the single response should contain a property "oc:meta-path-for-user" with value "/davtest.txt" - Scenario: User can retrieve meta information of a file inside folder + Scenario: user can retrieve meta information of a file inside folder Given user "Alice" has created folder "testFolder" And user "Alice" has uploaded file with content "123" to "/testFolder/davtest.txt" When user "Alice" retrieves the meta information of file "/testFolder/davtest.txt" using the meta API @@ -215,7 +217,7 @@ Feature: dav-versions And the single response should contain a property "oc:meta-path-for-user" with value "/testFolder/davtest.txt" - Scenario: User cannot retrieve meta information of a file which is owned by somebody else + Scenario: user cannot retrieve meta information of a file which is owned by somebody else Given user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file with content "123" to "/davtest.txt " And we save it into "FILEID" @@ -223,7 +225,7 @@ Feature: dav-versions Then the HTTP status code should be "404" - Scenario Outline: User cannot retrieve meta information of a file that does not exist + Scenario Outline: user cannot retrieve meta information of a file that does not exist When user "Alice" retrieves the meta information of fileId "" using the meta API Then the HTTP status code should be "400" or "404" Examples: @@ -234,7 +236,7 @@ Feature: dav-versions | MTI4NGQyMzgtYWE5Mi00MmNlLWJkxzQtMGIwMDAwMDA5MTU2OjhjY2QyNzUxLTkwYTQtNDBmMi1iOWYzLTYxZWRmODQ0MjFmNA== | 1284d238-aa92-42ce-bd�4-0b0000009156:8ccd2751-90a4-40f2-b9f3-61edf84421f4 | with : and � sign | - Scenario: File versions sets back after getting deleted and restored from trashbin + Scenario: file versions sets back after getting deleted and restored from trashbin Given user "Alice" has uploaded file with content "Old Test Content." to "/davtest.txt" And user "Alice" has uploaded file with content "New Test Content." to "/davtest.txt" And the version folder of file "/davtest.txt" for user "Alice" should contain "1" element @@ -250,14 +252,14 @@ Feature: dav-versions And the content of file "/davtest.txt" for user "Alice" should be "Old Test Content." - Scenario: Upload the same file twice with the same mtime and a version is available + Scenario: upload the same file twice with the same mtime and a version is available Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API When user "Alice" uploads file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API Then the HTTP status code should be "204" And the version folder of file "/file.txt" for user "Alice" should contain "1" element - Scenario: Upload the same file more than twice with the same mtime and only one version is available + Scenario: upload the same file more than twice with the same mtime and only one version is available Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API When user "Alice" uploads file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API @@ -265,7 +267,7 @@ Feature: dav-versions And the version folder of file "/file.txt" for user "Alice" should contain "1" element - Scenario: Upload the same file twice with the same mtime and no version after restoring + Scenario: upload the same file twice with the same mtime and no version after restoring Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "file.txt" with mtime "Thu, 08 Aug 2019 04:18:13 GMT" using the WebDAV API When user "Alice" restores version index "1" of file "/file.txt" using the WebDAV API @@ -369,7 +371,7 @@ Feature: dav-versions And the content of file "/Shares/sharingfolder/sharefile.txt" for user "Carol" should be "First content" - Scenario Outline: Moving a file (with versions) into a shared folder as the sharee and as the sharer + Scenario Outline: moving a file (with versions) into a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -394,7 +396,7 @@ Feature: dav-versions | new | Brian | /testshare | - Scenario Outline: Moving a file (with versions) out of a shared folder as the sharee and as the sharer + Scenario Outline: moving a file (with versions) out of a shared folder as the sharee and as the sharer Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Brian" has created folder "/testshare" @@ -419,7 +421,7 @@ Feature: dav-versions | new | Brian | /testshare | - Scenario: Receiver tries to get file versions of unshared file from the sharer + Scenario: receiver tries to get file versions of unshared 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 "textfile1" to "textfile1.txt" @@ -430,7 +432,7 @@ Feature: dav-versions And the value of the item "//s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound" @skipOnStorage:ceph - Scenario: Receiver tries get file versions of shared file from the sharer + 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" @@ -442,7 +444,7 @@ Feature: dav-versions Then the HTTP status code should be "403" - Scenario: Receiver tries get file versions of shared file before receiving it + Scenario: receiver tries get file versions of shared file before receiving it 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" diff --git a/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature b/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature index 95f6a00c443..d77ca43137f 100644 --- a/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature +++ b/tests/acceptance/features/coreApiWebdavDelete/deleteFolderContents.feature @@ -8,7 +8,7 @@ Feature: delete folder contents Given user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: Removing everything of a folder + Scenario Outline: removing everything from a folder Given using DAV path And user "Alice" has created folder "/PARENT/" And user "Alice" has created folder "/FOLDER/" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature index 68d928a55b4..b188a358e9f 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature @@ -1,5 +1,8 @@ @api Feature: propagation of etags when deleting a file or folder + As a client app + I want metadata (etags) of parent folders to change when a file or folder is deleted + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -82,7 +85,7 @@ Feature: propagation of etags when deleting a file or folder | spaces | - Scenario Outline: as share receiver deleting a file changes the etags of all parents for all collaborators + Scenario Outline: sharee deleting a file changes the etags of all parents for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload/sub" @@ -113,7 +116,7 @@ Feature: propagation of etags when deleting a file or folder | new | - Scenario Outline: as sharer deleting a file changes the etags of all parents for all collaborators + Scenario Outline: sharer deleting a file changes the etags of all parents for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload/sub" @@ -144,7 +147,7 @@ Feature: propagation of etags when deleting a file or folder | new | @issue-product-280 - Scenario Outline: as share receiver deleting a folder changes the etags of all parents for all collaborators + Scenario Outline: sharee deleting a folder changes the etags of all parents for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload/sub" @@ -175,7 +178,7 @@ Feature: propagation of etags when deleting a file or folder | new | @issue-product-280 - Scenario Outline: as sharer deleting a folder changes the etags of all parents for all collaborators + Scenario Outline: sharer deleting a folder changes the etags of all parents for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload/sub" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature index 715e8df4756..0c12125b7f8 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature @@ -1,5 +1,8 @@ @api Feature: propagation of etags when moving files or folders + As a client app + I want metadata (etags) of parent folder(s) to change when a file or folder is moved + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -155,7 +158,7 @@ Feature: propagation of etags when moving files or folders | spaces | - Scenario Outline: as share receiver renaming a file inside a folder changes its etag for all collaborators + Scenario Outline: sharee renaming a file inside a folder changes its etag for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload" @@ -182,7 +185,7 @@ Feature: propagation of etags when moving files or folders | new | - Scenario Outline: as sharer renaming a file inside a folder changes its etag for all collaborators + Scenario Outline: sharer renaming a file inside a folder changes its etag for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload" @@ -209,7 +212,7 @@ Feature: propagation of etags when moving files or folders | new | @issue-product-280 - Scenario Outline: as sharer moving a file from one folder to an other changes the etags of both folders for all collaborators + Scenario Outline: sharer moving a file from one folder to an other changes the etags of both folders for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/src" @@ -243,7 +246,7 @@ Feature: propagation of etags when moving files or folders | new | - Scenario Outline: as share receiver moving a file from one folder to an other changes the etags of both folders for all collaborators + Scenario Outline: sharee moving a file from one folder to an other changes the etags of both folders for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/src" @@ -277,7 +280,7 @@ Feature: propagation of etags when moving files or folders | new | @issue-product-280 - Scenario Outline: as sharer moving a folder from one folder to an other changes the etags of both folders for all collaborators + Scenario Outline: sharer moving a folder from one folder to an other changes the etags of both folders for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/src" @@ -311,7 +314,7 @@ Feature: propagation of etags when moving files or folders | new | - Scenario Outline: as share receiver moving a folder from one folder to an other changes the etags of both folders for all collaborators + Scenario Outline: sharee moving a folder from one folder to an other changes the etags of both folders for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/src" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature index df6b6308eb8..5b985164653 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature @@ -1,5 +1,8 @@ @api Feature: propagation of etags when copying files or folders + As a client app + I want metadata (etags) of parent folders to change when a file of folder is copied + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -152,7 +155,7 @@ Feature: propagation of etags when copying files or folders | spaces | - Scenario Outline: as share receiver copying a file inside a folder changes its etag for all collaborators + Scenario Outline: sharee copying a file inside a folder changes its etag for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload" @@ -189,7 +192,7 @@ Feature: propagation of etags when copying files or folders | new | @issue-product-280 - Scenario Outline: as sharer copying a file inside a folder changes its etag for all collaborators + Scenario Outline: sharer copying a file inside a folder changes its etag for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/upload" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature index dee0b75322a..89179697ef5 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature @@ -1,5 +1,8 @@ @api Feature: propagation of etags when creating folders + As a client app + I want metadata (etags) of parent folders to change when a sub-folder is created + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -52,7 +55,7 @@ Feature: propagation of etags when creating folders | spaces | @issue-product-280 - Scenario Outline: as share receiver creating a folder inside a folder received as a share changes its etag for all collaborators + Scenario Outline: sharee creating a folder inside a folder received as a share changes its etag for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/folder" @@ -78,7 +81,7 @@ Feature: propagation of etags when creating folders | new | @issue-product-280 - Scenario Outline: as a sharer creating a folder inside a shared folder changes etag for all collaborators + Scenario Outline: sharer creating a folder inside a shared folder changes etag for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has created folder "/folder" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature index 3536355ecf1..928a98edb9d 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreFromTrash.feature @@ -1,5 +1,8 @@ @api Feature: propagation of etags when restoring a file or folder from trash + As a client app + I want metadata (etags) of parent folders to change when a file or folder is restored + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature index 0188bd0d146..6afa40c6859 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/restoreVersion.feature @@ -1,5 +1,8 @@ @api @issue-product-280 Feature: propagation of etags when restoring a version of a file + As a client app + I want metadata (etags) of parent folders to change when a file version is restored + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given using OCS API version "2" @@ -7,7 +10,7 @@ Feature: propagation of etags when restoring a version of a file And user "Alice" has been created with default attributes and without skeleton files @skipOnStorage:ceph @skipOnStorage:scality - Scenario: Restoring a file changes the etags of all parents + Scenario: restoring a file changes the etags of all parents Given user "Alice" has created folder "/upload" And user "Alice" has created folder "/upload/sub" And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt" diff --git a/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature b/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature index 87ec179834b..fe411df3617 100644 --- a/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature +++ b/tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature @@ -1,5 +1,8 @@ @api Feature: propagation of etags when uploading data + As a client app + I want metadata (etags) of parent folders to change when a file is uploaded + So that the client app can know to re-scan and sync the content of the folder(s) Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -51,7 +54,7 @@ Feature: propagation of etags when uploading data | spaces | @issue-product-280 - Scenario Outline: as share receiver uploading a file inside a received shared folder should update etags for all collaborators + Scenario Outline: sharee uploading a file inside a received shared folder should update etags for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has shared folder "/upload" with user "Brian" @@ -76,7 +79,7 @@ Feature: propagation of etags when uploading data | new | @issue-product-280 - Scenario Outline: as sharer uploading a file inside a shared folder should update etags for all collaborators + Scenario Outline: sharer uploading a file inside a shared folder should update etags for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has shared folder "/upload" with user "Brian" @@ -101,7 +104,7 @@ Feature: propagation of etags when uploading data | new | - Scenario Outline: as share receiver overwriting a file inside a received shared folder should update etags for all collaborators + Scenario Outline: sharee overwriting a file inside a received shared folder should update etags for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" @@ -127,7 +130,7 @@ Feature: propagation of etags when uploading data | new | - Scenario Outline: as sharer overwriting a file inside a shared folder should update etags for all collaborators + Scenario Outline: sharer overwriting a file inside a shared folder should update etags for all collaborators Given user "Brian" has been created with default attributes and without skeleton files And using DAV path And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt" diff --git a/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature b/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature index 6ebf271ac82..2632a9f12d2 100644 --- a/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature +++ b/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature @@ -1,11 +1,14 @@ @api @issue-1284 Feature: there can be only one exclusive lock on a resource + As a user + I want to lock a resource + So that other users cannot access or change that resource Background: Given user "Alice" has been created with default attributes and without skeleton files - Scenario Outline: a second lock cannot be set on a folder when its exclusively locked + Scenario Outline: second lock cannot be set on a folder when its exclusively locked Given using DAV path And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" And user "Alice" has locked file "textfile0.txt" setting the following properties @@ -28,7 +31,7 @@ Feature: there can be only one exclusive lock on a resource | spaces | exclusive | - Scenario Outline: a share receiver cannot lock a resource exclusively locked by itself + Scenario Outline: sharee cannot lock a resource exclusively locked by itself Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" @@ -55,7 +58,7 @@ Feature: there can be only one exclusive lock on a resource | spaces | exclusive | - Scenario Outline: a share receiver cannot lock a resource exclusively locked by the owner + Scenario Outline: sharee cannot lock a resource exclusively locked by the owner Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" @@ -82,7 +85,7 @@ Feature: there can be only one exclusive lock on a resource | spaces | exclusive | - Scenario Outline: a share owner cannot lock a resource exclusively locked by a share receiver + Scenario Outline: sharer cannot lock a resource exclusively locked by a sharee Given using DAV path And user "Brian" has been created with default attributes and without skeleton files And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt" diff --git a/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature b/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature index f451e0f551d..01e30903b40 100644 --- a/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature +++ b/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature @@ -1,5 +1,8 @@ @api @issue-1284 Feature: actions on a locked item are possible if the token is sent with the request + As a user + I want to share the lock token of a resource + So that the users or apps can access the resource that I have locked Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature b/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature index da1e1cca1d5..ae9620cd11c 100644 --- a/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature +++ b/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature @@ -1,6 +1,8 @@ @api @issue-1284 -Feature: independent locks - Make sure all locks are independent and don't interact with other items that have the same name +Feature: independent locks - make sure all locks are independent and don't interact with other items that have the same name + As a user + I want to lock resources independently + So that resources with same name in other parts of the file system will not be locked Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature b/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature index b0e017479d0..5a3fd9ebbfc 100644 --- a/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature +++ b/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature @@ -1,6 +1,8 @@ @api @issue-1284 -Feature: independent locks - Make sure all locks are independent and don't interact with other items that have the same name +Feature: independent locks - make sure all locks are independent and don't interact with other items that have the same name + As a user + I want to independently lock resources shared with me + So that resources with same name in other received shares will not be locked Background: Given user "Alice" has been created with default attributes and without skeleton files diff --git a/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature b/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature index 26811a6e2ba..7ea61382dc4 100644 --- a/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature +++ b/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature @@ -1,5 +1,8 @@ @api @issue-1284 -Feature: UNLOCK locked items +Feature: Unlock locked items + As a user + I want to unlock the resources previously locked by myself + So that other users can make changes to the resources Background: Given user "Alice" has been created with default attributes and without skeleton files @@ -26,7 +29,7 @@ Feature: UNLOCK locked items | spaces | - Scenario Outline: as public unlocking a file in a share that was locked by the file owner is not possible. To unlock use the owners locktoken + Scenario Outline: public unlocking a file in a share that was locked by the file owner is not possible. To unlock use the owners locktoken Given user "Alice" has created folder "PARENT" And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" And user "Alice" has created a public link share of folder "PARENT" with change permission diff --git a/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature b/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature index 43626189249..c19b342cf3d 100644 --- a/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature +++ b/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature @@ -1,5 +1,8 @@ @api @issue-1284 Feature: UNLOCK locked items (sharing) + As a user + I want to unlock a shared resource that has been locked by me to be restricted + So that other users cannot unlock the shared resource Background: Given these users have been created with default attributes and without skeleton files: @@ -10,7 +13,7 @@ Feature: UNLOCK locked items (sharing) And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt" - Scenario Outline: as share receiver unlocking a shared file locked by the file owner is not possible. To unlock use the owners locktoken + Scenario Outline: unlocking a shared file that has been locked by the file owner is not feasible unless the owner lock tocken is used Given using DAV path And user "Alice" has locked file "PARENT/parent.txt" setting the following properties | lockscope | | @@ -34,7 +37,7 @@ Feature: UNLOCK locked items (sharing) | spaces | exclusive | /parent.txt | - Scenario Outline: as share receiver unlocking a file in a share locked by the file owner is not possible. To unlock use the owners locktoken + Scenario Outline: sharee cannot unlock a file within a shared folder when it is locked by the file owner unless the owner lock token is used Given using DAV path And user "Alice" has locked file "PARENT/parent.txt" setting the following properties | lockscope | | @@ -58,7 +61,7 @@ Feature: UNLOCK locked items (sharing) | spaces | exclusive | - Scenario Outline: as share receiver unlock a shared file + Scenario Outline: sharee unlock a shared file Given using DAV path And user "Alice" has shared file "PARENT/parent.txt" with user "Brian" And user "Brian" has accepted share "" offered by user "Alice" @@ -106,7 +109,7 @@ Feature: UNLOCK locked items (sharing) | spaces | exclusive | /parent.txt | - Scenario Outline: as owner unlocking a file in a share that was locked by the share receiver is not possible. To unlock use the receivers locktoken + Scenario Outline: unlocking a file in a shared folder, which was locked by the sharee is not possible for the owner unless the receiver's locktoken is used Given using DAV path And user "Alice" has shared folder "PARENT" with user "Brian" And user "Brian" has accepted share "/PARENT" offered by user "Alice"