test(NODE-3719): separate change stream prose tests #3113
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nbbeeken
approved these changes
Jan 24, 2022
nbbeeken
suggested changes
Jan 24, 2022
Contributor
nbbeeken
left a comment
nbbeeken
left a comment
There was a problem hiding this comment.
hold on merging, I missed part of reviewing this.
nbbeeken
suggested changes
Jan 24, 2022
nbbeeken
approved these changes
Jan 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
NODE-3719
What is changing?
Separating prose tests from the general change stream test file.
Also noticed a crud prose test in the wrong place, so moved that, too.
Also noticed duplicate/strangely implemented versioned api test and deleted it (it's covered in the mongo_client unit tests).
Is there new documentation needed for these changes?
N/A
What is the motivation for this change?
Spec compliance review
Double check the following
npm run check:lintscript<type>(NODE-xxxx)<!>: <description>