aboutsummaryrefslogtreecommitdiffstats
path: root/build/integration/sharing_features/sharing-v1-part2.feature
Commit message (Collapse)AuthorAgeFilesLines
* chore: Add SPDX headerAndy Scherzinger2024-06-061-0/+2
| | | | Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
* Fix copy in view-only modeVincent Petry2022-08-261-0/+20
| | | | Signed-off-by: Vincent Petry <vincent@nextcloud.com>
* Add int test for view-only downloadVincent Petry2022-08-261-0/+20
| | | | | | Asserts that downloading a view-only document returns 403. Signed-off-by: Vincent Petry <vincent@nextcloud.com>
* Fix unauthorized OCS status in provisioningJoas Schilling2021-05-121-1/+1
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Add more integration tests for resharing permissionsDaniel Calviño Sánchez2020-07-091-0/+244
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Accept incoming shares in integration testsDaniel Calviño Sánchez2019-11-201-0/+41
| | | | | | | | | Now all incoming shares need to be explicitly accepted before being able to use the shared file or get information about a reshare (although getting the information of the incoming share is possible before accepting it). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add more integration tests for getting sharesDaniel Calviño Sánchez2019-10-261-0/+124
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Add integration tests for getting shares including subfilesDaniel Calviño Sánchez2019-10-251-0/+186
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Fix shares read permissionsJohn Molakvoæ (skjnldsv)2019-10-041-2/+32
| | | | | | | A user with reshare permissions on a file is now able to get any share of that file (just like the owner). Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
* Add assorted integration tests for sharesDaniel Calviño Sánchez2019-10-041-0/+21
| | | | Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Do not expect a 200 HTTP status code when updating a shareDaniel Calviño Sánchez2019-10-041-0/+3
| | | | | | | | | | | | | This will be needed to test scenarios in which updating a share return a different HTTP status code, like 401. The assertion for the 200 HTTP status code was added in those scenarios that tested updating a share (that is, those that were also checking the OCS status code), but not in those in which updating a share was just a preparatory step for the actual test (in the same way that the HTTP status code is not checked in those tests when creating a share). Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
* Move sharing integration tests to their own directoryJohn Molakvoæ (skjnldsv)2019-10-041-0/+521
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>