a test collecting all non-equality operators in the filters to find #162
Conversation
This file contains 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
|
If this is a test of the API more than astrapy itself, maybe this could go to another test file/suite ? |
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.
I am not even sure such a test belongs to astrapy, in a sense (astrapy's role as a passthrough for the payload is somewhat trivial here) - on the other hand it could help early discovery of regressions elsewhere. WDYT?
(this comes from an equivalent Java test, where the role of the sdk is more substantial since it's a fluent-interface "builder" kind of thing. I'm open to trash this or merge, whatever the consensus is).