You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be easy to figure out what runs when. Test files shouldn't be including/excluding anything with nested if's or checking whether we are running with or without plugins.
Refactor the test setup.
By default all test are unit tests and should all run without requiring an actual OpenSearch instance.
A folder called integ should contain integration tests that can be run in bulk and require an OpenSearch instance.
If we want to keep plugin tests separate, then there should be a plugins/<name of plugin> folder to run those.
CI/CD should invoke unit tests by default, and integration tests otherwise across a matrix of versions.
The text was updated successfully, but these errors were encountered:
What is the bug?
Coming from #823 (comment), there's some code that defines "server tests" which makes it difficult to know what tests actually run in
opensearch-py/test_opensearchpy/run_tests.py
Lines 159 to 164 in a24b9f3
So what tests actually run and when?
What is the expected behavior?
It should be easy to figure out what runs when. Test files shouldn't be including/excluding anything with nested
if
's or checking whether we are running with or without plugins.Refactor the test setup.
integ
should contain integration tests that can be run in bulk and require an OpenSearch instance.plugins/<name of plugin>
folder to run those.CI/CD should invoke unit tests by default, and integration tests otherwise across a matrix of versions.
The text was updated successfully, but these errors were encountered: