a7526d74ae
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> |
||
|---|---|---|
| .. | ||
| capabilities_features | ||
| config | ||
| data | ||
| features | ||
| federation_features | ||
| filesdrop_features | ||
| ldap_features | ||
| remoteapi_features | ||
| setup_features | ||
| sharees_features | ||
| sharing_features | ||
| .gitignore | ||
| composer.json | ||
| run-docker.sh | ||
| run.sh | ||