WARNING: Version 1.5 of Elasticsearch has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

› › ›

integration tests

edit

integration tests

edit

These kind of tests require firing up a whole cluster of nodes, before the tests can actually be run. Compared to unit tests they are obviously way more time consuming, but the test infrastructure tries to minimize the time cost by only restarting the whole cluster, if this is configured explicitly.

The class your tests have to inherit from is ElasticsearchIntegrationTest. As soon as you inherit, there is no need for you to start any elasticsearch nodes manually in your test anymore, though you might need to ensure that at least a certain number of nodes is up.

number of shards

edit

The number of shards used for indices created during integration tests is randomized between 1 and 10 unless overwritten upon index creation via index settings. Rule of thumb is not to specify the number of shards unless needed, so that each test will use a different one all the time.

generic helper methods

edit

There are a couple of helper methods in ElasticsearchIntegrationTest, which will make your tests shorter and more concise.

`refresh()`	Refreshes all indices in a cluster
`ensureGreen()`	Ensures a green health cluster state, waiting for relocations. Waits the default timeout of 30 seconds before failing.
`ensureYellow()`	Ensures a yellow health cluster state, also waits for 30 seconds before failing.
`createIndex(name)`	Creates an index with the specified name
`flush()`	Flushes all indices in a cluster
`flushAndRefresh()`	Combines `flush()` and `refresh()` calls
`optimize()`	Waits for all relocations and optimized all indices in the cluster to one segment.
`indexExists(name)`	Checks if given index exists
`admin()`	Returns an `AdminClient` for administrative tasks
`clusterService()`	Returns the cluster service java class
`cluster()`	Returns the test cluster class, which is explained in the next paragraphs

test cluster methods

edit

The TestCluster class is the heart of the cluster functionality in a randomized test and allows you to configure a specific setting or replay certain types of outages to check, how your custom code reacts.

`ensureAtLeastNumNodes(n)`	Ensure at least the specified number of nodes is running in the cluster
`ensureAtMostNumNodes(n)`	Ensure at most the specified number of nodes is running in the cluster
`getInstance()`	Get a guice instantiated instance of a class from a random node
`getInstanceFromNode()`	Get a guice instantiated instance of a class from a specified node
`stopRandomNode()`	Stop a random node in your cluster to mimic an outage
`stopCurrentMasterNode()`	Stop the current master node to force a new election
`stopRandomNonMaster()`	Stop a random non master node to mimic an outage
`buildNode()`	Create a new elasticsearch node
`startNode(settings)`	Create and start a new elasticsearch node

Accessing clients

edit

In order to execute any actions, you have to use a client. You can use the ElasticsearchIntegrationTest.client() method to get back a random client. This client can be a TransportClient or a NodeClient - and usually you do not need to care as long as the action gets executed. There are several more methods for client selection inside of the TestCluster class, which can be accessed using the ElasticsearchIntegrationTest.cluster() method.

`iterator()`	An iterator over all available clients
`masterClient()`	Returns a client which is connected to the master node
`nonMasterClient()`	Returns a client which is not connected to the master node
`clientNodeClient()`	Returns a client, which is running on a client node
`client(String nodeName)`	Returns a client to a given node
`smartClient()`	Returns a smart client

Scoping

edit

By default the tests are run with unique cluster per test suite. Of course all indices and templates are deleted between each test. However, sometimes you need to start a new cluster for each test - for example, if you load a certain plugin, but you do not want to load it for every test.

You can use the @ClusterScope annotation at class level to configure this behaviour

@ClusterScope(scope=TEST, numNodes=1)
public class CustomSuggesterSearchTests extends ElasticsearchIntegrationTest {
  // ... tests go here
}

The above sample configures the test to use a new cluster for each test method. The default scope is SUITE (one cluster for all test methods in the test). The numNodes settings allows you to only start a certain number of nodes, which can speed up test execution, as starting a new node is a costly and time consuming operation and might not be needed for this test.

Changing node configuration

edit

As elasticsearch is using JUnit 4, using the @Before and @After annotations is not a problem. However you should keep in mind, that this does not have any effect in your cluster setup, as the cluster is already up and running when those methods are run. So in case you want to configure settings - like loading a plugin on node startup - before the node is actually running, you should overwrite the nodeSettings() method from the ElasticsearchIntegrationTest class and change the cluster scope to SUITE.

@Override
protected Settings nodeSettings(int nodeOrdinal) {
  return ImmutableSettings.settingsBuilder()
           .put("plugin.types", CustomSuggesterPlugin.class.getName())
           .put(super.nodeSettings(nodeOrdinal)).build();
}

« unit tests parameterized tests »