-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[PM-13274] [Unified] Add integration tests for creating and updating collections #5814
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
[PM-13274] [Unified] Add integration tests for creating and updating collections #5814
Conversation
…dding-a-group-to-a-collection-returns-500-error---but-works
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5814 +/- ##
==========================================
+ Coverage 47.54% 50.78% +3.24%
==========================================
Files 1651 1651
Lines 74814 74814
Branches 6724 6724
==========================================
+ Hits 35569 37994 +2425
+ Misses 37787 35301 -2486
- Partials 1458 1519 +61 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
New Issues (1)Checkmarx found the following issues in this Pull Request
|
…ection-returns-500-error---but-works
…ection-returns-500-error---but-works
|
🎟️ Tracking
Main ticket: https://bitwarden.atlassian.net/browse/PM-21799
Relates to:
📔 Objective
I was unable to reproduce the linked issues, however I took the opportunity to add db integration tests (which run on all our db providers) to confirm this. No other changes at this stage.
Vault changes are just moving the
CollectionRepositoryTests
into AC Team ownership.📸 Screenshots
⏰ 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