Skip to content
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

[tests-only][full-ci] added test to update share role to existing role after the assigned share role is disabled #10760

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

PrajwolAmatya
Copy link
Contributor

@PrajwolAmatya PrajwolAmatya commented Dec 11, 2024

Description

This PR adds test to update share role to an existing role after the assigned share role is disabled. This PR covers the test for updating the roles to:

  • Secure Viewer to other existing permissions role (Personal Space resource)
  • Secure Viewer to other existing permissions role (Project Space resource)
  • Space Editor Without Versions to other existing permissions role

Currently, trying to update the permissions role from Denied to other existing permissions role takes more than 30 seconds to sync, which makes the tests execution longer. So, currently scenario related to updating the permissions role from Denied to other roles has been removed from this PR and will be added on the next PR and move this PR forward as this PR has been on hold for long time.

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests only (no source changes)

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:

@PrajwolAmatya PrajwolAmatya force-pushed the update-share-role branch 2 times, most recently from a8dc67b to 13e34ac Compare December 18, 2024 06:17
@PrajwolAmatya PrajwolAmatya force-pushed the update-share-role branch 5 times, most recently from be48232 to 892d1a6 Compare December 23, 2024 03:33
@PrajwolAmatya
Copy link
Contributor Author

Moving this PR to in progress to update according to comment https://github.com/owncloud/ocis/pull/10744/files#r1899452910

Ready for review 👀

Copy link
Member

@SagarGi SagarGi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@nabim777
Copy link
Member

nabim777 commented Jan 9, 2025

LGTM 👍

@PrajwolAmatya PrajwolAmatya force-pushed the update-share-role branch 3 times, most recently from 95ead98 to eef0ee2 Compare January 10, 2025 03:52
| space | Personal |
| resource | <resource> |
Then the HTTP status code should be "200"
And the updated permissions role of the last share should be "<permissions-role>"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it like checking the response object?

Suggested change
And the updated permissions role of the last share should be "<permissions-role>"
And the updated permissions role of the last share should be "<permissions-role>"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not the whole response, but only the value of the role id.

Copy link
Member

@saw-jan saw-jan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@PrajwolAmatya PrajwolAmatya merged commit 2279b8f into master Jan 14, 2025
4 checks passed
@PrajwolAmatya PrajwolAmatya deleted the update-share-role branch January 14, 2025 09:31
ownclouders pushed a commit that referenced this pull request Jan 14, 2025
[tests-only][full-ci] added test to update share role to existing role after the assigned share role is disabled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants