anchor.diff:  See the usage, by passing -h, to see how to filter test classes.
   You can pass a regex which is checked against the full class name; so, part of class name can be used.
   IntegrationTestsDriver uses Junit to run the tests.
  -Currently there is no support for running integration tests against a distributed cluster using maven (see link:https://issues.apache.org/jira/browse/HBASE-6201[HBASE-6201]). 
  +Currently there is no support for running integration tests against a distributed cluster using maven (see link:https://issues.apache.org/jira/browse/HBASE-6201[HBASE-6201]).
   
   The tests interact with the distributed cluster by using the methods in the `DistributedHBaseCluster` (implementing `HBaseCluster`) class, which in turn uses a pluggable `ClusterManager`.
   Concrete implementations provide actual functionality for carrying out deployment-specific and environment-dependent tasks (SSH, etc). The default `ClusterManager` is `HBaseClusterManager`, which uses SSH to remotely execute start/stop/kill/signal commands, and assumes some posix commands (ps, etc). Also assumes the user running the test has enough "power" to start/stop servers on the remote machines.
   By default, it picks up `HBASE_SSH_OPTS`, `HBASE_HOME`, `HBASE_CONF_DIR` from the env, and uses `bin/hbase-daemon.sh` to carry out the actions.
   Currently tarball deployments, deployments which uses _hbase-daemons.sh_, and link:http://incubator.apache.org/ambari/[Apache Ambari]                    deployments are supported.
   _/etc/init.d/_ scripts are not supported for now, but it can be easily added.
  -For other deployment options, a ClusterManager can be implemented and plugged in. 
  +For other deployment options, a ClusterManager can be implemented and plugged in.
   
   [[maven.build.commands.integration.tests.destructive]]
   ==== Destructive integration / system tests
  
positive.code: ----
  +
  This command copies all artifacts up to a temporary staging Apache mvn repository in an 'open' state.
  More work needs to be done on these maven artifacts to make them generally available. 
  +
  We do not release HBase tarball to the Apache Maven repository. To avoid deploying the tarball, do not include the `assembly:single` goal in your `mvn deploy` command. Check the deployed artifacts as described in the next section.
  
  
negative.code: ----
  
  If you just want to run the integration tests in top-level, you need to run two commands.
  First: +mvn failsafe:integration-test+ This actually runs ALL the integration tests.
  
  NOTE: This command will always output `BUILD SUCCESS` even if there are test failures.
  
  At this point, you could grep the output by hand looking for failed tests.
  However, maven will do this for us; just use: +mvn
  