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] Test coverage for federated user trying to delete deleted federation connection #11017

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

anon-pradip
Copy link
Contributor

@anon-pradip anon-pradip commented Feb 17, 2025

Description

This PR adds up the following scenario to test: federated user trying to delete deleted federation connection

Scenario: federated user tries to delete previously deleted federated connection

Related Issue

Part of: #10971
Bug report: #10223

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:

@anon-pradip anon-pradip self-assigned this Feb 17, 2025
@anon-pradip anon-pradip force-pushed the test/test-coverage-for-deleted-user branch from a1b5880 to 7888b35 Compare February 17, 2025 09:15
@anon-pradip anon-pradip force-pushed the test/test-coverage-for-deleted-user branch from 7888b35 to 935ba4c Compare February 17, 2025 10:15
@anon-pradip anon-pradip changed the title [tests-only][full-ci] Test coverage for trying to delete deleted user [tests-only][full-ci] Test coverage for federated user trying to delete deleted federation connection Feb 17, 2025
@anon-pradip anon-pradip marked this pull request as ready for review February 17, 2025 11:09
@@ -132,3 +132,13 @@ Feature: delete federated connections
}
}
"""

@issue-10223
Scenario: federated user tries to delete previously deleted federated connection
Copy link
Member

Choose a reason for hiding this comment

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

also, try to test these behaviors if possible
#10223 (comment)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Okeii.. I will make another follow-up PR. 👍

@anon-pradip anon-pradip force-pushed the test/test-coverage-for-deleted-user branch from 935ba4c to 9f8585e Compare February 19, 2025 08:14
@prashant-gurung899
Copy link
Contributor

LGTM 👍

@anon-pradip anon-pradip force-pushed the test/test-coverage-for-deleted-user branch 2 times, most recently from 85d12e5 to 6094f61 Compare February 26, 2025 08:21
@anon-pradip anon-pradip force-pushed the test/test-coverage-for-deleted-user branch from 6094f61 to 1a5d5cd Compare February 26, 2025 09:40
@issue-10223
Scenario: federated user tries to delete previously deleted federated connection
Given user "Brian" has deleted federated connection with user "Alice"
When user "Brian" tries to delete federated connection with user "Alice" using the Graph API
Copy link
Contributor

Choose a reason for hiding this comment

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

Would the behavior be same if Alice tries to delete the federated connection here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. It gives 400 (Bad request) when Alice tries to delete the federated connection that has already been deleted by her. We can have test coverage for this scenario also. Will add in the follow-up PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

better to add in this PR, rather than follow-up

@anon-pradip anon-pradip force-pushed the test/test-coverage-for-deleted-user branch from 1a5d5cd to 8aad2a1 Compare February 26, 2025 11:50
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.

5 participants