[tests-only][full-ci] removed steps related to share api occ commands (#6096)

* removed steps related to occ commands

* removed scenarios from expected failures

* fixed lines in exp failure
This commit is contained in:
Prajwol Amatya
2023-05-10 10:13:11 +05:45
committed by GitHub
parent 7dd1114966
commit 1788406b52
14 changed files with 34 additions and 489 deletions

View File

@@ -157,17 +157,16 @@ File and sync features in a shared scenario
#### [ocs sharing api always returns an empty exact list while searching for a sharee](https://github.com/owncloud/ocis/issues/4265)
- [coreApiSharees/sharees.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L100)
- [coreApiSharees/sharees.feature:101](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L101)
- [coreApiSharees/sharees.feature:102](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L102)
- [coreApiSharees/sharees.feature:120](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L120)
- [coreApiSharees/sharees.feature:121](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L121)
- [coreApiSharees/sharees.feature:122](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L122)
- [coreApiSharees/sharees.feature:140](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L140)
- [coreApiSharees/sharees.feature:141](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L141)
- [coreApiSharees/sharees.feature:142](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L142)
- [coreApiSharees/sharees.feature:160](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L160)
- [coreApiSharees/sharees.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L161)
- [coreApiSharees/sharees.feature:162](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L162)
- [coreApiSharees/sharees.feature:180](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L180)
- [coreApiSharees/sharees.feature:181](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L181)
- [coreApiSharees/sharees.feature:182](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharees/sharees.feature#L182)
#### [accepting matching name shared resources from different users/groups sets no serial identifiers on the resource name for the receiver](https://github.com/owncloud/ocis/issues/4289)
@@ -220,7 +219,7 @@ cannot share a folder with create permission
- [coreApiShareOperationsToShares1/gettingShares.feature:190](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L190)
#### [Public link enforce permissions](https://github.com/owncloud/ocis/issues/1269)
- [coreApiSharePublicLink1/createPublicLinkShare.feature:356](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature#L356)
- [coreApiSharePublicLink1/createPublicLinkShare.feature:355](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature#L355)
#### [download previews of other users file](https://github.com/owncloud/ocis/issues/2071)
@@ -242,7 +241,7 @@ cannot share a folder with create permission
#### [Upload-only shares must not overwrite but create a separate file](https://github.com/owncloud/ocis/issues/1267)
- [coreApiSharePublicLink3/uploadToPublicLinkShare.feature:10](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature#L10)
- [coreApiSharePublicLink3/uploadToPublicLinkShare.feature:131](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature#L131)
- [coreApiSharePublicLink3/uploadToPublicLinkShare.feature:111](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink3/uploadToPublicLinkShare.feature#L111)
#### [Set quota over settings](https://github.com/owncloud/ocis/issues/1290)
@@ -295,45 +294,11 @@ cannot share a folder with create permission
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:32](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L32)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L33)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:84](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L84)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L85)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:141](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L141)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:142](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L142)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:199](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L199)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:200](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L200)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:201](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L201)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:202](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L202)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:285](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L285)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:286](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L286)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:316](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L316)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:317](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L317)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:318](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L318)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:319](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L319)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:377](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L377)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:378](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L378)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:379](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L379)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:380](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L380)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:381](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L381)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:382](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L382)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:411](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L411)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:412](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L412)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:413](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L413)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:414](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L414)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:442](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L442)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:443](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L443)
#### Expiration date of group shares
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L58)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:59](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L59)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:114](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L114)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:115](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L115)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:170](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L170)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:171](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L171)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:230](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L230)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:231](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L231)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:232](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L232)
- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:233](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L233)
#### [Cannot move folder/file from one received share to another](https://github.com/owncloud/ocis/issues/2442)
@@ -400,7 +365,7 @@ API, search, favorites, config, capabilities, not existing endpoints, CORS and o
- [coreApiAuthOcs/ocsGETAuth.feature:124](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiAuthOcs/ocsGETAuth.feature#L124)
- [coreApiAuthOcs/ocsPOSTAuth.feature:11](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiAuthOcs/ocsPOSTAuth.feature#L11)
- [coreApiAuthOcs/ocsPUTAuth.feature:11](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiAuthOcs/ocsPUTAuth.feature#L11)
- [coreApiSharePublicLink1/createPublicLinkShare.feature:346](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature#L346)
- [coreApiSharePublicLink1/createPublicLinkShare.feature:345](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiSharePublicLink1/createPublicLinkShare.feature#L345)
#### [sending MKCOL requests to another user's webDav endpoints as normal user gives 404 instead of 403 ](https://github.com/owncloud/ocis/issues/3872)
@@ -549,6 +514,7 @@ And other missing implementation of favorites
#### [Trying to accept a share with invalid ID gives incorrect OCS and HTTP status](https://github.com/owncloud/ocis/issues/2111)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L85)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:86](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L86)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:87](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L87)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:88](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L88)
@@ -556,20 +522,18 @@ And other missing implementation of favorites
- [coreApiShareOperationsToShares2/shareAccessByID.feature:90](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L90)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:91](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L91)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:92](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L92)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:93](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L93)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:105](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L105)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:106](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L106)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L103)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:104](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L104)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:134](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L134)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:135](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L135)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:136](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L136)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:137](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L137)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:138](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L138)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:139](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L139)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:140](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L140)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:141](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L141)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:142](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L142)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:143](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L143)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:144](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L144)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:156](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L156)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:157](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L157)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:152](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L152)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:153](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L153)
#### [Shares to deleted group listed in the response](https://github.com/owncloud/ocis/issues/2441)
@@ -628,8 +592,8 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
- [coreApiShareManagementToShares/acceptShares.feature:183](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L183)
- [coreApiShareManagementToShares/acceptShares.feature:228](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L228)
- [coreApiShareManagementToShares/acceptShares.feature:438](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L438)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:124](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L124)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L125)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:122](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L122)
- [coreApiShareOperationsToShares2/shareAccessByID.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L123)
- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:178](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L178)
- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:179](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L179)
- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:180](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L180)

View File

@@ -57,22 +57,6 @@ class AppConfigurationContext implements Context {
$this->modifyAppConfig($app, $parameter, $value);
}
/**
* @Given /^parameter "([^"]*)" of app "([^"]*)" has been set to ((?:'[^']*')|(?:"[^"]*"))$/
*
* @param string $parameter
* @param string $app
* @param string $value
*
* @return void
* @throws Exception
*/
public function serverParameterHasBeenSetTo(string $parameter, string $app, string $value):void {
// The capturing group of the regex always includes the quotes at each
// end of the captured string, so trim them.
return;
}
/**
* @Then the capabilities setting of :capabilitiesApp path :capabilitiesPath should be :expectedValue
* @Given the capabilities setting of :capabilitiesApp path :capabilitiesPath has been confirmed to be :expectedValue

View File

@@ -5,8 +5,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
So that I can keep my file system clean
Background:
Given parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using OCS API version "1"
Given using OCS API version "1"
And using new DAV path
And these users have been created with default attributes and without skeleton files:
| username |

View File

@@ -75,8 +75,7 @@ Feature: share access by ID
Scenario Outline: accept a share using the invalid share Id
Given parameter "shareapi_auto_accept_share" of app "core" has been set to "yes"
And using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs_api_version>"
When user "Brian" accepts share with ID "<share_id>" using the sharing API
Then the OCS status code should be "404"
And the HTTP status code should be "<http_status_code>"
@@ -94,8 +93,7 @@ Feature: share access by ID
Scenario Outline: accept a share using empty share Id
Given parameter "shareapi_auto_accept_share" of app "core" has been set to "yes"
And using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs_api_version>"
When user "Brian" accepts share with ID "" using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"
@@ -118,16 +116,15 @@ Feature: share access by ID
| /Shares/textfile0.txt |
And the sharing API should report to user "Brian" that these shares are in the declined state
| path |
| <declined_share_path> |
| /Shares/textfile0.txt |
Examples:
| ocs_api_version | ocs_status_code | declined_share_path |
| 1 | 100 | /Shares/textfile0.txt |
| 2 | 200 | /Shares/textfile0.txt |
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: decline a share using a invalid share Id
Given parameter "shareapi_auto_accept_share" of app "core" has been set to "yes"
And using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs_api_version>"
When user "Brian" declines share with ID "<share_id>" using the sharing API
Then the OCS status code should be "404"
And the HTTP status code should be "<http_status_code>"
@@ -145,8 +142,7 @@ Feature: share access by ID
Scenario Outline: decline a share using empty share Id
Given parameter "shareapi_auto_accept_share" of app "core" has been set to "yes"
And using OCS API version "<ocs_api_version>"
Given using OCS API version "<ocs_api_version>"
When user "Brian" declines share with ID "" using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "<http_status_code>"

View File

@@ -219,7 +219,6 @@ Feature: create a public link share
Scenario Outline: creating a link share with no specified permissions defaults to read permissions when public upload is disabled globally and accessing using the public WebDAV API
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_allow_public_upload" of app "core" has been set to "no"
And user "Alice" has created folder "/afolder"
When user "Alice" creates a public link share using the sharing API with settings
| path | /afolder |

View File

@@ -98,26 +98,6 @@ Feature: upload to a public link share
When the public uploads file "test.txt" with content "test-file" using the new public WebDAV API
Then the HTTP status code should be "507"
@issue-1328
Scenario: Uploading file to a public shared folder does not work when allow public uploads has been disabled before sharing and again enabled after sharing the folder with public API
Given parameter "shareapi_allow_public_upload" of app "core" has been set to "no"
And user "Alice" has created a public link share with settings
| path | FOLDER |
And parameter "shareapi_allow_public_upload" of app "core" has been set to "yes"
When the public uploads file "test.txt" with content "test-file" using the new public WebDAV API
And the HTTP status code should be "403"
@issue-1328
Scenario: Uploading file to a public shared folder works when allow public uploads has been disabled and again enabled after sharing the folder with public API
Given user "Alice" has created a public link share with settings
| path | FOLDER |
| permissions | create |
And parameter "shareapi_allow_public_upload" of app "core" has been set to "no"
And parameter "shareapi_allow_public_upload" of app "core" has been set to "yes"
When the public uploads file "test.txt" with content "test-file" using the new public WebDAV API
Then the HTTP status code should be "201"
And the content of file "/FOLDER/test.txt" for user "Alice" should be "test-file"
@smokeTest
Scenario: Uploading to a public upload-write and no edit and no overwrite share with public API
Given user "Alice" has created a public link share with settings

View File

@@ -11,7 +11,6 @@ Feature: resharing can be disabled
Scenario Outline: ordinary sharing is allowed when allow resharing has been disabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_allow_resharing" of app "core" has been set to "no"
When user "Alice" shares file "/textfile0.txt" with user "Brian" with permissions "share,update,read" using the sharing API
Then the OCS status code should be "<ocs_status_code>"
And the HTTP status code should be "200"

View File

@@ -59,271 +59,8 @@ Feature: resharing a resource with an expiration date
| 2 | 200 |
Scenario Outline: resharing with user using the sharing API with expire days set and combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | <expected-expire-date> |
And the response when user "Carol" gets the info of the last share should include
| expiration | <expected-expire-date> |
Examples:
| ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code |
| 1 | yes | +30 days | 100 |
| 2 | yes | +30 days | 200 |
| 1 | no | | 100 |
| 2 | no | | 200 |
@issue-1289
Scenario Outline: resharing with group using the sharing API with expire days set and combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_group_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And group "grp1" has been created
And user "Carol" has been added to group "grp1"
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | group |
| permissions | change |
| shareWith | grp1 |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | <expected-expire-date> |
And the response when user "Carol" gets the info of the last share should include
| expiration | <expected-expire-date> |
Examples:
| ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code |
| 1 | yes | +30 days | 100 |
| 2 | yes | +30 days | 200 |
| 1 | no | | 100 |
| 2 | no | | 200 |
Scenario Outline: resharing with user using the sharing API without expire days set and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | <expected-expire-date> |
And the response when user "Carol" gets the info of the last share should include
| expiration | <expected-expire-date> |
Examples:
| ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code |
| 1 | yes | +7 days | 100 |
| 2 | yes | +7 days | 200 |
| 1 | no | | 100 |
| 2 | no | | 200 |
@issue-1289
Scenario Outline: resharing with group using the sharing API without expire days set and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes"
And user "Carol" has been created with default attributes and without skeleton files
And group "grp1" has been created
And user "Carol" has been added to group "grp1"
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | group |
| permissions | change |
| shareWith | grp1 |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | <expected-expire-date> |
And the response when user "Carol" gets the info of the last share should include
| expiration | <expected-expire-date> |
Examples:
| ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code |
| 1 | yes | +7 days | 100 |
| 2 | yes | +7 days | 200 |
| 1 | no | | 100 |
| 2 | no | | 200 |
Scenario Outline: resharing with user using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
| expireDate | +20 days |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | +20 days |
And the response when user "Carol" gets the info of the last share should include
| expiration | +20 days |
Examples:
| ocs_api_version | default-expire-date | ocs_status_code |
| 1 | yes | 100 |
| 2 | yes | 200 |
| 1 | no | 100 |
| 2 | no | 200 |
@issue-1289
Scenario Outline: resharing with group using the sharing API with expire days set and with combinations of default/enforce expire date enabled and specify expire date in share
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_group_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_group_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_group_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And group "grp1" has been created
And user "Carol" has been added to group "grp1"
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | group |
| permissions | change |
| shareWith | grp1 |
| expireDate | +20 days |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | +20 days |
And the response when user "Carol" gets the info of the last share should include
| expiration | +20 days |
Examples:
| ocs_api_version | default-expire-date | ocs_status_code |
| 1 | yes | 100 |
| 2 | yes | 200 |
| 1 | no | 100 |
| 2 | no | 200 |
Scenario Outline: Setting default expiry date and enforcement after the share is created
Given using OCS API version "<ocs_api_version>"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
And user "Brian" has shared file "/Shares/textfile0.txt" with user "Carol"
And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "4"
When user "Brian" gets the info of the last share using the sharing API
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And the information of the last share of user "Brian" should include
| expiration | |
And the response when user "Carol" gets the info of the last share should include
| expiration | |
Examples:
| ocs_api_version | default-expire-date | ocs_status_code |
| 1 | yes | 100 |
| 2 | yes | 200 |
| 1 | no | 100 |
| 2 | no | 200 |
@issue-1289
Scenario Outline: resharing group share with user using the sharing API with default expire date set and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And group "grp1" has been created
And user "Carol" has been created with default attributes and without skeleton files
And user "Brian" has been added to group "grp1"
And user "Alice" has shared file "/textfile0.txt" with group "grp1" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | <expected-expire-date> |
And the response when user "Carol" gets the info of the last share should include
| expiration | <expected-expire-date> |
Examples:
| ocs_api_version | default-expire-date | expected-expire-date | ocs_status_code |
| 1 | yes | +30 days | 100 |
| 2 | yes | +30 days | 200 |
| 1 | no | | 100 |
| 2 | no | | 200 |
@issue-1289
Scenario Outline: resharing group share with user using the sharing API with default expire date set and specifying expiration on share and with combinations of default/enforce expire date enabled
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And group "grp1" has been created
And user "Carol" has been created with default attributes and without skeleton files
And user "Brian" has been added to group "grp1"
And user "Alice" has shared file "/textfile0.txt" with group "grp1" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
| expireDate | +20 days |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Brian" should include
| expiration | +20 days |
And the response when user "Carol" gets the info of the last share should include
| expiration | +20 days |
Examples:
| ocs_api_version | default-expire-date | ocs_status_code |
| 1 | yes | 100 |
| 2 | yes | 200 |
| 1 | no | 100 |
| 2 | no | 200 |
Scenario Outline: resharing using the sharing API with default expire date set but not enforced
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "no"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
@@ -340,104 +77,6 @@ Feature: resharing a resource with an expiration date
And the response when user "Carol" gets the info of the last share should include
| expiration | |
Examples:
| ocs_api_version | default-expire-date | ocs_status_code |
| 1 | yes | 100 |
| 2 | yes | 200 |
| 1 | no | 100 |
| 2 | no | 200 |
Scenario Outline: reshare extends the received expiry date up to the default by default
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "<enforce-expire-date>"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has created a share with settings
| path | textfile0.txt |
| shareType | user |
| permissions | all |
| shareWith | Brian |
| expireDate | +20 days |
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
Then the HTTP status code should be "200"
And the OCS status code should be "<ocs_status_code>"
And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
And the information of the last share of user "Alice" should include
| expiration | +20 days |
And the response when user "Carol" gets the info of the last share should include
| expiration | +20 |
Examples:
| ocs_api_version | default-expire-date | enforce-expire-date | ocs_status_code |
| 1 | yes | yes | 100 |
| 2 | yes | yes | 200 |
| 1 | yes | no | 100 |
| 2 | yes | no | 200 |
| 1 | no | no | 100 |
| 2 | no | no | 200 |
Scenario Outline: reshare cannot extend the received expiry date further into the future
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "<default-expire-date>"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "no"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has created a share with settings
| path | textfile0.txt |
| shareType | user |
| permissions | all |
| shareWith | Brian |
| expireDate | +20 days |
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
| expireDate | +40 days |
#The action of changing the expiration date while resharing should be forbidden
Then the HTTP status code should be "403"
And the OCS status code should be "403"
And the information of the last share of user "Alice" should include
| expiration | +20 days |
Examples:
| ocs_api_version | default-expire-date |
| 1 | yes |
| 2 | yes |
| 1 | no |
| 2 | no |
Scenario Outline: reshare cannot extend the received expiry date past the default when the default is enforced
Given using OCS API version "<ocs_api_version>"
And parameter "shareapi_default_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_enforce_expire_date_user_share" of app "core" has been set to "yes"
And parameter "shareapi_expire_after_n_days_user_share" of app "core" has been set to "30"
And user "Carol" has been created with default attributes and without skeleton files
And user "Alice" has created a share with settings
| path | textfile0.txt |
| shareType | user |
| permissions | all |
| shareWith | Brian |
| expireDate | +20 days |
And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
When user "Brian" creates a share using the sharing API with settings
| path | /Shares/textfile0.txt |
| shareType | user |
| permissions | change |
| shareWith | Carol |
| expireDate | +40 days |
Then the HTTP status code should be "403"
And the OCS status code should be "403"
And the information of the last share of user "Alice" should include
| expiration | +20 days |
Examples:
| ocs_api_version |
| 1 |
| 2 |
| ocs_api_version | ocs_status_code |
| 1 | 100 |
| 2 | 200 |

View File

@@ -60,13 +60,12 @@ Feature: search sharees
Scenario Outline: search only with group members - allowed
Given using OCS API version "<ocs-api-version>"
And parameter "shareapi_only_share_with_group_members" of app "core" has been set to "yes"
And user "Sharee1" has been added to group "ShareeGroup2"
When user "Alice" gets the sharees using the sharing API with parameters
| search | sharee |
| itemType | file |
Then the OCS status code should be "<ocs-status>"
And the HTTP status code should be "<http-status>"
And the HTTP status code should be "200"
And the "exact users" sharees returned should be empty
And the "users" sharees returned should be
| Sharee One | 0 | sharee1 |
@@ -77,9 +76,9 @@ Feature: search sharees
And the "exact remotes" sharees returned should be empty
And the "remotes" sharees returned should be empty
Examples:
| ocs-api-version | ocs-status | http-status |
| 1 | 100 | 200 |
| 2 | 200 | 200 |
| ocs-api-version | ocs-status |
| 1 | 100 |
| 2 | 200 |
Scenario Outline: search with exact match
@@ -207,7 +206,6 @@ Feature: search sharees
| username | displayname |
| another | Another |
And user "Another" has been added to group "ShareeGroup2"
And parameter "shareapi_share_dialog_user_enumeration_group_members" of app "core" has been set to "yes"
When user "Alice" gets the sharees using the sharing API with parameters
| search | anot |
| itemType | file |

View File

@@ -3,7 +3,6 @@ Feature: propagation of etags when deleting a file or folder
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And user "Alice" has created folder "/upload"
@@ -147,7 +146,6 @@ Feature: propagation of etags when deleting a file or folder
@issue-product-280
Scenario Outline: as share receiver 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/upload/sub"
And user "Alice" has created folder "/upload/sub/toDelete"
@@ -179,7 +177,6 @@ Feature: propagation of etags when deleting a file or folder
@issue-product-280
Scenario Outline: as 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/upload/sub"
And user "Alice" has created folder "/upload/sub/toDelete"

View File

@@ -157,7 +157,6 @@ Feature: propagation of etags when moving files or folders
Scenario Outline: as share receiver 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/upload"
And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
@@ -185,7 +184,6 @@ Feature: propagation of etags when moving files or folders
Scenario Outline: as 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/upload"
And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
@@ -213,7 +211,6 @@ Feature: propagation of etags when moving files or folders
@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
Given user "Brian" has been created with default attributes and without skeleton files
And parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/src"
And user "Alice" has created folder "/dst"
@@ -248,7 +245,6 @@ Feature: propagation of etags when moving files or folders
Scenario Outline: as share receiver 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/src"
And user "Alice" has created folder "/dst"
@@ -283,7 +279,6 @@ Feature: propagation of etags when moving files or folders
@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
Given user "Brian" has been created with default attributes and without skeleton files
And parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/src"
And user "Alice" has created folder "/dst"
@@ -318,7 +313,6 @@ Feature: propagation of etags when moving files or folders
Scenario Outline: as share receiver 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/src"
And user "Alice" has created folder "/dst"

View File

@@ -154,7 +154,6 @@ Feature: propagation of etags when copying files or folders
Scenario Outline: as share receiver 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/upload"
And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
@@ -192,7 +191,6 @@ Feature: propagation of etags when copying files or folders
@issue-product-280
Scenario Outline: as 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 parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And using <dav_version> DAV path
And user "Alice" has created folder "/upload"
And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"

View File

@@ -3,7 +3,6 @@ Feature: propagation of etags when creating folders
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
@issue-product-280
Scenario Outline: creating a folder inside a folder changes its etag

View File

@@ -3,7 +3,6 @@ Feature: propagation of etags when uploading data
Background:
Given user "Alice" has been created with default attributes and without skeleton files
And parameter "shareapi_auto_accept_share" of app "core" has been set to "no"
And user "Alice" has created folder "/upload"
@issue-product-280