-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[API Acceptance Tests] Test exceptional case in all ocs routes #34566
Comments
GitMate.io thinks the contributor most likely able to help you is @phil-davis. Possibly related issues are #22485 (test), #22492 (test), #31579 (test), #32040 (fix API acceptance tests), and #31403 (Expand API acceptance tests). |
List of endpoints (including endpoints added by bundled apps) and tested response
List of endpoints that are tested for correct authentication
|
I've to looks through what is tested
|
It would be great to have a API specification first and issue contract based testing in order to ensure the contracts ( and the error cases ) are done properly :-) |
the second table shows the progress of testing ocs endpoints for correct / incorrect authentications |
CORS tests #34665 |
a couple of more CORS tests #34697 |
I think we have covered most of the important cases, closing this issue. Feel free to reopen if more cases need to be covered |
did you say specification? https://www.freedesktop.org/wiki/Specifications/open-collaboration-services/ |
Background
When migrating from legacy OCS Api implementations to OCSController we are breaking behavior in exceptional cases. Instead of proper OCS response with proper xml/json body a pure JSON response is returned. PR to fix this will follow.
Actions
Add api acceptance tests for ALL ocs routes (needed because of the migration path to make sure we hit everything properly).
Test following exceptional scenarios:
All scenarios need to be executed as CORS requests and non CORS requests (analyse CORS requests with wrong origin header as well)
Test Targets
The text was updated successfully, but these errors were encountered: