* Try to run linter and unit test from top-level directory
Instead of starting a separate pipeline for each service we now just run
the linter and unit tests from the top-level directory. This allows us
to run the linter it with '--modules-download-mode vendor' and should also
reduce the resource usage.
* cleanup: remove no longer valid submodule release step
---------
Co-authored-by: Ralf Haferkamp <rhaferkamp@owncloud.com>
pass the returned response without setting in then step
added the missing when step whose response is checked by the then step
addressed the reviews
changed from decoded body to docoded response
* log request-response to a file
show logs in ci
move hooks to one place
* preserve logs between suites
* ignore logs
* Refactor and beautify logs
* fix php style
* add log step in ci pipeline
* get expected-failure file from env if available
refactored given steps
refactored some when stepa
refactored remaining when and then steps
use of when step for the action
changed line no in expected failure
remove and add same kind of steps in the scenario and refactored function names
adressing reviews
* refactoring webdav context (setting response in when step only)
refactoring the given steps in the webdav context
refactored remaining given/when/then steps
return file id
trim trailing from the folder path
add missing when step and make other minor corrections
set responseXml and correct status code check
correct the naming of steps and helper functions
* setting response
* refactor given and when steps in webdavproperties context
* change the status code in tests as the when step sets the response now
* correct the status code check
* only save response
* use getResponseXml to get xml response object
* fix isEtagValid method
* rename step def methods
* make stricter checks
---------
Co-authored-by: Saw-jan <saw.jan.grg3e@gmail.com>
refactor given and when steps in ocs and webdav locking context
use the returned response
use of returned response from helper function
made changes to the affected test steps
deleted vardump line
* use default config for OCDAV_ALLOW_PROPFIND_DEPTH_INFINITY
* remove unnecessary steps
* use default propfind depth infinity value
* use correct step to check the resources
* use correct step to check the resources
* cover depth:infinity enabled test cases
* fix steps
* fix scenario steps
* update expected failure list
* add depth infinity test suite to ci
* update existing tests only
* remove test with depth:infinity
- Use var for common errors
- Add the addition error message to the Error() output of errorcode.Error
- in PatchEducationSchool() use errorcode.RenderError() to turn the errorcode
in to the right HTTP Status (instead of return 500 always)
(cherry picked from commit a34d467285)
An LDAP Modify operation never returns LDAPResultEntryAlreadyExists errors.
That error can only happen for LDAPAdd or LDAPModifyDN.
(cherry picked from commit ce808eaa17)
