-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-25949] ExternalCallback Integration tests for SSO Project #6809
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
Conversation
…e substitutes with mocked responses, where possible.
|
|
…com/bitwarden/server into auth/pm-25949/sso-integration-tests
|
Claude finished @ike-kottlowski's task in 2m 49s —— View job Review Status: Re-review CompleteThis is a re-review following commit SummaryGood work fixing the Changes Since Last Review
Review FindingsParameter Naming ConventionFile: The parameter public async Task ExternalCallback_WithInvalidUserIdentifierFormat_ReturnsError(
string UserIdentifier // Should be: userIdentifier
)Overall AssessmentThe PR successfully adds comprehensive integration test coverage for SSO ExternalCallback scenarios, including:
The minor production code changes (typo fix + TODO comment) are appropriate and low-risk. Generated with Claude Code |
…ject with SSO integration test which match the integration test factory pattern more closely.
bitwarden_license/test/Sso.IntegrationTest/Utilities/SsoTestDataBuilder.cs
Outdated
Show resolved
Hide resolved
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6809 +/- ##
==========================================
+ Coverage 55.26% 55.70% +0.44%
==========================================
Files 1939 1939
Lines 86224 86224
Branches 7705 7705
==========================================
+ Hits 47655 48035 +380
+ Misses 36777 36379 -398
- Partials 1792 1810 +18 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|


🎟️ Tracking
PM-25949
📔 Objective
In order to support a refactor coming down the pipe from the Admin Console team we needed to ensure that the Just-In-Time provisioning will have parity with the new work.
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes