Query operator tests for multiple index types #800
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
Tests consistent behaviour for handling null values and range queries between different index types (_all_docs, json indexes and text indexes).
wohali
pushed a commit
that referenced
this pull request
Oct 19, 2017
* add operator tests for text indexes * add operator tests for _all_docs * add tests for null and range handling Tests consistent behaviour for handling null values and range queries between different index types (_all_docs, json indexes and text indexes).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Overview
Mango operator tests previously only ran against json indexes. This PR ensures they also run against a database with no indexes (i.e. verify "pure" selector behaviour) as well as against json indexes and text indexes (when available). The intention here is to catch any inconsistencies or change in results that might occur due to the index selected (clearly we don't want results to change because a user adds an index!).
Note that text indexes do not currently pass these tests, but are not exercised as part of the CouchDB test suite.
Testing recommendations
Ensure the test suite runs (CI should handle this).
GitHub issue number
Related Pull Requests
Checklist