Set up an "integration test" environment with Blimpy

Blimpfile

@@ -4,5 +4,7 @@
 Blimpy.fleet do |fleet|
   fleet.add(:aws) do |ship|
     ship.name = 'sauceconnector'
+    ship.livery = :cwd
+    ship.flavor = 'm1.small'
   end
 end

bootstrap.sh

@@ -0,0 +1,18 @@
+#!/bin/sh -x
+
+export PATH=/var/lib/gems/1.8/bin:$PATH
+
+which puppet
+
+if [ $? -ne 0 ]; then
+    apt-get update
+
+    apt-get install -y ruby1.8 \
+                    ruby1.8-dev \
+                    libopenssl-ruby1.8 \
+                    rubygems
+
+    gem install puppet --no-ri --no-rdoc
+fi
+
+puppet apply --verbose --modulepath=../ tests/init.pp

tests/init.pp

@@ -1,11 +1,10 @@
-# The baseline for module testing used by Puppet Labs is that each manifest
-# should have a corresponding test manifest that declares that class or defined
-# type.
-#
-# Tests are then run by using puppet apply --noop (to check for compilation errors
-# and view a log of events) or by fully applying the test in a virtual environment
-# (to compare the resulting system state to the desired state).
-#
-# Learn more about module testing here: http://docs.puppetlabs.com/guides/tests_smoke.html
-#
-include sauceconnect
+node default {
+  group {
+    'puppet' :
+      ensure => present;
+  }
+
+  class {
+    'sauceconnect' : ;
+  }
+}