Daniel Calviño Sánchez a7526d74ae Do not expect a 200 HTTP status code when updating a share ... 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>		2019-10-04 19:25:10 +02:00
..
capabilities_features	Add intergration tests	2016-04-04 19:35:01 +02:00
config	Move sharing integration tests to their own directory	2019-10-04 19:25:10 +02:00
data	Don't set Content-Disposition header if one already exists	2016-12-14 17:35:27 +01:00
features	Do not expect a 200 HTTP status code when updating a share	2019-10-04 19:25:10 +02:00
federation_features	Disable failing federated sharing tests	2019-03-13 18:01:24 +01:00
filesdrop_features	Add intergration tests	2016-12-02 13:17:53 +01:00
ldap_features	add LDAP integr. test for receiving share candidates with group limitation	2019-06-14 06:23:58 +02:00
remoteapi_features	Some tests for the remote cloud api	2017-12-08 16:34:33 +01:00
setup_features	Add integration test for web based installer	2016-11-21 22:00:16 +01:00
sharees_features	200 is ok	2017-03-20 13:13:09 -06:00
sharing_features	Do not expect a 200 HTTP status code when updating a share	2019-10-04 19:25:10 +02:00
.gitignore	Adding missing files	2015-09-29 13:42:32 +02:00
composer.json	Update sabre/dav requirement from 3.2.2 to 3.2.3 in /build/integration	2018-10-22 17:11:57 +00:00
run-docker.sh	Add helper script to run integration tests on a Docker container	2019-10-04 19:25:10 +02:00
run.sh	Add install logic for enable command	2019-02-19 21:03:06 +01:00