@Override
  public InternalCache getCache() {
    return locator.getCache();
  }
This is a rule to start up a locator in your current VM. It's useful for your Integration Tests.

<p>
This rules allows you to create/start a locator using any @ConfigurationProperties, you can chain
the configuration of the rule like this: LocatorStarterRule locator = new LocatorStarterRule()
.withProperty(key, value) .withName(name) .withProperties(properties) .withSecurityManager(class)
.withJmxManager() etc, etc. If your rule calls withAutoStart(), the locator will be started
before your test code.

<p>
In your test code, you can use the rule to access the locator's attributes, like the port
information, working dir, name, and the InternalLocator it creates.

<p>
by default the rule starts a locator with jmx and cluster configuration service
you can turn off cluster configuration service to have your test
run faster if your test does not need them.

http service can be started when needed in your test.
<p>
If you need a rule to start a server/locator in different VMs for Distributed tests, You should
use {@code ClusterStartupRule}.
geode-dunit/src/main/java/org/apache/geode/test/junit/rules/LocatorStarterRule.java