-
Notifications
You must be signed in to change notification settings - Fork 189
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
Test coverage for setting api #8800
Comments
We have this api but we have replaced many of the settings api endpoinds with a graph I wouldn't put any more effort into it than that. I would just created setting feature and check that it works without edge cases. |
What about the security of the endpoint? |
As per our monthly QA meeting on 2024-12-13, we decided to add basic happy tests for the settings APIs that are still in use. |
|
Describe
OCIS has provided documentation for grpc-setting. However, there's an issue tagged as #1349 regarding the documentation of an API endpoint, yet no corresponding pull request has been linked to it. Notably, there isn't specific test coverage dedicated to the setting API. However, the setting API has been employed to meet prerequisites and verify outcomes for features related to notifications and roles.
Overview of used setting API on OCIS API tests
https://github.com/owncloud/ocis/blob/c179485db65d92fa2bb96e48cb01fa92e125d497/tests/acceptance/features/bootstrap/SettingsContext.php contain all code related to setting API
settings endpoint =
/api/v0/settings/
2.getRoleIdByRoleName->getRoles
2.@given /^the administrator has given "([^"])" the role "([^"]*)" using the settings api$/
2.userChangeOwnRole->assignRoleToUser
3. userChangeRoleAnotherUser->assignRoleToUser
2. @when /^user "([^"])" changes his own role to "([^"])"$/
3. @when /^user "([^"])" changes the role "([^"])" for user "([^"]*)"$/
2. userShouldHaveRole->getAssignmentsList
2. @then /^user "([^"])" should have the role "([^"]*)"$/
2. listAllNotifications->getSettingLanguageValue->sendRequestGetSettingsValuesList
Point to discuss
The text was updated successfully, but these errors were encountered: