Vagrant-Binding-Demos

This projects offers some demos and tutorials for the use of Vagrant-Binding. You can use this as a base for your own integration of Vagrant-Binding in your projects and UnitTests.

DbHandlerTest

This UnitTest checks the functionality of the DbHandler class. This class offers some simple methods for the work with a mysql database. You can connect to a existing mysql server by jdbc and create some dummy data in it. The UnitTests checks this functions. Normally a UnitTest like the given on has some problems:

• The mySQL server must be available
• The tables must be empty at the start of the test
• you can not run the test parallel to other UnitTests that use the database or the same tables

For this type of UnitTests people often use a in-memory database like Derby or H2. But sometimes you have to use a specific database. With the Vagrant-Binding you can exclude all the mentioned problems. Vagrant-Bindings offers a JUnit Rule for you that works like a wrapper around your UnitTests. With the VagrantTestRule you can sync all your tests with the lifecycle of virtual machines. In the DbHandler example a VagrantTestRule is defined with the configuration of a vm that runs MySQL server on it. The vm will be created and started before every test. When the test finishes the vm will be destroyed. So you can run your tests in parallel because every on uses its own virtual machine. The vm is created on startup with a new and empty MySQL Server on it. So you will never have a problem with old data again. The vm for this test is created by a Vagrant / Puppet config that is created by Java code: First we configure the puppet files. Every puppet scipt need a path and a filename for the Puppet manifest.

PuppetProvisionerConfig puppetConfig = PuppetProvisionerConfigBuilder
    .create()
    .withManifestPath("puppet/manifests")
    .withManifestFile("dbserver.pp")
    .withDebug(true)
    .build();

We take a internal file as the Puppet manifest. This file configures the complete MySQL server installation:

VagrantFileTemplateConfiguration fileTemplateConfiguration2 = VagrantFileTemplateConfigurationBuilder
    .create()
    .withUrlTemplate(VagrantUtils.getInstance().load("com/guigarage/vagrant/dbhandler/dbserver.pp"))
    .withPathInVagrantFolder("puppet/manifests/dbserver.pp")
    .build();

The MySQL installation needs a configfile. We also use a internal file:

VagrantFileTemplateConfiguration fileTemplateConfiguration1 = VagrantFileTemplateConfigurationBuilder
		.create()
			.withUrlTemplate(VagrantUtils.getInstance().load("com/guigarage/vagrant/dbhandler/my.cnf"))
			.withPathInVagrantFolder("files/my.cnf")
			.build();

Next to Puppet we need a Vagrant configuration for the vm. We take the default "Lucid32" Vagrant template and configure a static ip for the vm:

VagrantVmConfig vmConfig = VagrantVmConfigBuilder
    .create()
    .withName("mysqlvm")
    .withHostOnlyIp(VM_IP)
    .withLucid32Box()
    .withPuppetProvisionerConfig(puppetConfig)
    .build();

Now we putting all together:

VagrantEnvironmentConfig environmentConfig = VagrantEnvironmentConfigBuilder
    .create()
    .withVagrantVmConfig(vmConfig)
    .build();

VagrantConfiguration configuration = VagrantConfigurationBuilder
    .create()
    .withVagrantEnvironmentConfig(environmentConfig)
    .withVagrantFileTemplateConfiguration(fileTemplateConfiguration1)
    .withVagrantFileTemplateConfiguration(fileTemplateConfiguration2)
    .build();

The VagrantConfiguration is finally used by the VagrantTestRule.