anchor.diff:  
   == Testing packaging
   
  -The packaging tests use Vagrant virtual machines to verify that installing
  -and running elasticsearch distributions works correctly on supported operating systems.
  -These tests should really only be run in vagrant vms because they're destructive.
  +The packaging tests use Vagrant virtual machines or cloud instances to verify
  +that installing and running Elasticsearch distributions works correctly on
  +supported operating systems. These tests should really only be run on ephemeral
  +systems because they're destructive; that is, these tests install and remove
  +packages and freely modify system settings, so you will probably regret it if
  +you execute them on your development machine.
  +
  +When you run a packaging test, Gradle will set up the target VM and mount your
  +repository directory in the VM. Once this is done, a Gradle task will issue a
  +Vagrant command to run a *nested* Gradle task on the VM. This nested Gradle
  +runs the actual "destructive" test classes.
   
   . Install Virtual Box and Vagrant.
   +
  
positive.code: 
  === Load balancing and caches.
  
  By default the tests run on multiple processes using all the available cores on all 
  available CPUs. Not including hyper-threading.
  If you want to explicitly specify the number of JVMs you can do so on the command
  line:
  
negative.code: == Test coverage analysis
  
  Generating test coverage reports for Elasticsearch is currently not possible through Gradle.
  However, it _is_ possible to gain insight in code coverage using IntelliJ's built-in coverage
  analysis tool that can measure coverage upon executing specific tests. Eclipse may also be able
  to do the same using the EclEmma plugin.
  
  