Assert multiple result-sets in tSQLt.AssertResultSetsHaveSameMetaData#85
Open
TheConstructor wants to merge 1 commit intotSQLt-org:mainfrom
Open
Conversation
TheConstructor
force-pushed
the
feature/assert-metadata-of-multiple-result-sets
branch
from
9943b94 to
1a2fa4c
Compare
Author
|
@mbt1 have you found time to look at this? Is there anything that should be different? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Enhance tSQLt.AssertResultSetsHaveSameMetaData to assert all returned result-sets. To make evaluating the assert easier, the result-set-number is prefixed and each result-set is presented on a separate line.
The documentation already sounds like multiple result-sets are asserted, so this might help people making accidental misassumptions.