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] add test to check add and remove member acivities #9824

Merged
merged 1 commit into from
Aug 19, 2024

Conversation

prashant-gurung899
Copy link
Contributor

@prashant-gurung899 prashant-gurung899 commented Aug 16, 2024

Description

This PR adds test where a sharer checks api activities of a space after a member is added and removed.

Scenario: check add member to space activity
Scenario: check remove member from space activity

Related Issue

Motivation and Context

How Has This Been Tested?

  • locally
  • CI

Screenshots (if appropriate):

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:

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.

LGTM 👍
Please, rebase and resolve the conflicts

Signed-off-by: prashant-gurung899 <[email protected]>
Copy link

@saw-jan saw-jan merged commit eac382a into master Aug 19, 2024
4 checks passed
@saw-jan saw-jan deleted the api-activities-member branch August 19, 2024 11:24
ownclouders pushed a commit that referenced this pull request Aug 19, 2024
[tests-only][full-ci] add test to check add and remove member acivities
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.

2 participants