-
Notifications
You must be signed in to change notification settings - Fork 409
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
Verify that client metadata not being mutated #3194
Verify that client metadata not being mutated #3194
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3194 +/- ##
==========================================
- Coverage 75.43% 74.49% -0.95%
==========================================
Files 420 421 +1
Lines 26179 26238 +59
==========================================
- Hits 19748 19545 -203
- Misses 5299 5518 +219
- Partials 1132 1175 +43
... and 36 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After fixing the problem with closure, you can run the new test against MongoDB only:
go test -count=1 -run='TestMutatingClientMetadata' -target-url=mongodb://127.0.0.1:47017/ -target-backend=mongodb .
It seems to me that the test fails.
Hi @rumyantseva thanks! With regard to running the single integration test I was trying to follow previous approach - |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for contributing! I tried the implementation and left my thoughts.
Hi @rumyantseva, Thank you very much for the review! I have pushed the required changes. |
@noisersup PTAL |
Co-authored-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
@kropidlowsky please re-request review if it is ready :) |
@AlekSi integration tests continue to explode. Can you please advise? I would appreciate it |
@kropidlowsky the root cause is fixed in be944e7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Thanks for your contribution 🤗
@rumyantseva PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description
Closes #2989.
Added support for verifying client metadata not being mutated
Readiness checklist
task all
, and it passed.@FerretDB/core
), Labels, Project and project's Sprint fields.