anchor.diff:  ----
   
   When `-Dtest` is specified, the `localTests` profile will be used.
  -Each junit test is executed in a separate JVM (A fork per test class). There is no parallelization when tests are running in this mode.
  +Each junit test is executed in a separate JVM (A fork per test class).
  +There is no parallelization when tests are running in this mode.
   You will see a new message at the end of the -report: `"[INFO] Tests are skipped"`.
  -It's harmless.
  -However, you need to make sure the sum of `Tests run:` in the `Results:` section of test reports matching the number of tests you specified because no error will be reported when a non-existent test case is specified.
  +It's harmless.  However, you need to make sure the sum of
  +`Tests run:` in the `Results:` section of test reports matching the number of tests
  +you specified because no error will be reported when a non-existent test case is specified.
   
   [[hbase.unittests.cmds.test.profiles]]
   ==== Other test invocation permutations
  
positive.code: You can then use it to run all HBase tests on 2.0 with the command:
  
  ----
  mvn test
                          -P runAllTests -Dsurefire.secondPartForkCount=12
                          -Dtest.build.data.basedirectory=/ram2G
  ----
  
  On earlier versions, use:
  
  ----
  mvn test
                          -P runAllTests -Dsurefire.secondPartThreadCount=12
                          -Dtest.build.data.basedirectory=/ram2G
  ----
  
  [[hbase.unittests.cmds.test.hbasetests]]
  
negative.code: [[hbase.unittests.test.faster]]
  ==== Running tests faster
  
  By default, `$ mvn test -P runAllTests` runs all tests using a quarter of the CPUs available on machine
  hosting the test run (see `surefire.firstPartForkCount` and `surefire.secondPartForkCount` in the top-level
  hbase `pom.xml`). Up these counts to get the build to run faster. You can also have hbase modules
  run their tests in parrallel when the dependency graph allows by passing `--threads=N` when you invoke
  maven, where `N` is the amount of parallelism wanted.
  
  For example, allowing that you want to use all cores on a machine to run tests,
  you could start up the maven test run with:
  
  ----
    $ x="1.0C";  mvn -Dsurefire.firstPartForkCount=$x -Dsurefire.secondPartForkCount=$x test -PrunAllTests
  ----
  
  If a 32 core machine, you should see periods during which 32 forked jvms appear in your process listing each running unit tests.
  Your milage may vary. Dependent on hardware, overcommittment of CPU, memory, etc., can bring the test suite crashing down,
  usually complaining of system exit and incomplete test report xml files. Start gently, with the default fork setting which
  uses a quarter of the available CPUs.
  
  Adding the `--threads=N`, maven will run N modules in parallel when dependencies allow. Be aware, if you have
  set the forkcount to `1.0C`, and the threads count to '2', the number of concurrent test runners can approach
  2 * CPU count likely overcommitting the host machine.
  
  You will need ~2.2GB of memory per forked JVM plus the memory used by maven itself (3-4G).
  
  
  To increase the speed, you can as well use a ramdisk. 2-3G should be sufficient. Be sure to
  delete the files between each test run. The typical way to configure a ramdisk on Linux is:
  
  ----
  $ sudo mkdir /ram2G
  