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
Copy file name to clipboardExpand all lines: TESTING.asciidoc
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -685,7 +685,10 @@ There are multiple base classes for tests:
685
685
These allow you to test functionality that is not exposed via the REST API, or for verifying a certain internal state.
686
686
Additionally, you can easily simulate tricky distributed setups that are difficult to do in REST tests.
687
687
If you only need to start one node, use `ESSingleNodeTestCase` instead, which is a much lighter test setup.
688
-
* **`ESRestTestCase`**: This should be the first choice for writing integration tests. These tests run in a much more realistic setup, and rely on REST APIs to talk to ES.
688
+
* **`ESRestTestCase`**: An integration test that interacts with an external
689
+
cluster via the REST API. This is used for Java based REST tests. This should
690
+
be the first choice for writing integration tests as these tests run in a much more
691
+
realistic setup.
689
692
* **`ESClientYamlSuiteTestCase` **: A subclass of `ESRestTestCase` used to run YAML based REST tests.
0 commit comments