recategorize two tests as integration tests #937
Merged
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
These tests are running as unit tests and starting an Elasticsearch server. To make the best use of ElasticsearchTestServer, we want all tests that use Elasticsearch to run in the same set of tests, so that we only start Elasticsearch once. This moves/renames those two tests so they run with all the other integration tests.
iWebi
approved these changes
Sep 16, 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.
These tests are running as unit tests and starting an Elasticsearch server. To make the best use of ElasticsearchTestServer, we want all tests that use Elasticsearch to run in the same set of tests, so that we only start Elasticsearch once. This moves/renames those two tests so they run with all the other integration tests.