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.
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
Changes to work with Databricks SDK
v0.38.0
#350Changes to work with Databricks SDK
v0.38.0
#350Changes from 3 commits
cac0b6e
c382b96
a316172
35cf424
4fe3911
e640d9c
2efca99
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
To check the result-set precisely,
results
needs to remain a list.Because the query orders the rows, order-sensitive equality checking is fine in this case.
It's not needed here, but in general for order-insensitive comparison the pattern is:
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.
I should clarify: right now this is performing neither an order-sensitive nor an order-insensitive check of the results, but rather something in-between.
In this case I think the comparison is supposed to be order-sensitive (because the query is), so please use lists for both
results
and the check against the expected set of results.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.
The example you provided does not work as
assert len(results) == len(expected)
will assert toFalse
as there are duplicates inresults
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.
I think the integration test is just there to test we get some output back