comments

Author: pabloem

TESTING.asciidoc

@@ -681,7 +681,10 @@ There are multiple base classes for tests:
   directly by unit tests.
 * **`ESSingleNodeTestCase`**: This test case sets up a cluster that has a
   single node.
-* **`ESIntegTestCase`**: An internal integration test that starts nodes within the same JVM as the test. These tests are excellent for testing internal functionality that is not exposed via the REST API, or for verifying a certain internal state. Additionally, you can easily simulate tricky distributed setups that are difficult to do in REST tests. If you only need to start one node, use `ESSingleNodeTestCase` instead, which is a much lighter test setup.
+* **`ESIntegTestCase`**: An internal integration test that starts nodes within the same JVM as the test.
+    These allow you to test functionality that is not exposed via the REST API, or for verifying a certain internal state.
+    Additionally, you can easily simulate tricky distributed setups that are difficult to do in REST tests.
+    If you only need to start one node, use `ESSingleNodeTestCase` instead, which is a much lighter test setup.
 * **`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.
 * **`ESClientYamlSuiteTestCase` **: A subclass of `ESRestTestCase` used to run YAML based REST tests.