anchor.diff:  [[test-cluster-methods]]
   ==== test cluster methods
   
  -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.
  +The `InternalTestCluster` 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.
   
   [horizontal]
   `ensureAtLeastNumNodes(n)`::        Ensure at least the specified number of nodes is running in the cluster
  
positive.code: [[using-elasticsearch-test-classes]]
  === Using the elasticsearch test classes
  
  First, you need to include the testing dependency in your project. If you use maven and its `pom.xml` file, it looks like this
  
  [[source,xml]]
  --------------------------------------------------
  <dependencies>
    <dependency>
      <groupId>com.carrotsearch.randomizedtesting</groupId>
      <artifactId>randomizedtesting-runner</artifactId>
      <version>${randomizedtesting-runner.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.apache.lucene</groupId>
      <artifactId>lucene-test-framework</artifactId>
  
negative.code: `randomLocale()`::      Returns a random locale
  `randomTimeZone()`::    Returns a random timezone
  
  `randomFrom()`::        Returns a random element from a list/array
  
  In addition, there are a couple of helper methods, allowing you to create random ASCII and Unicode strings, see methods beginning with `randomAscii`, `randomUnicode`, and `randomRealisticUnicode` in the random test class. The latter one tries to create more realistic unicode string by not being arbitrary random.
  
  If you want to debug a specific problem with a specific random seed, you can use the `@Seed` annotation to configure a specific seed for a test. If you want to run a test more than once, instead of starting the whole test suite over and over again, you can use the `@Repeat` annotation with an arbitrary value. Each iteration than gets run with a different seed.
  