87bc6ec63f
RSpec was chosen to be used for acceptance tests for many reasons: * The tests are actually much cleaner now. It is clearer to see what is being tested, and what is being used for setup. * Matcher transition will be coming soon. This will really clean up a lot of the "assert" boilerplate all over. There was a lot of repetition in this area. * Shared examples will help greatly for testing common error cases for many commands. * The test runner for RSpec is simply much better. Being able to specify the exact test to run by line, for example, is a great help.
45 lines
1.4 KiB
Ruby
45 lines
1.4 KiB
Ruby
require "yaml"
|
|
|
|
require "log4r"
|
|
|
|
module Acceptance
|
|
# This represents a configuration object for acceptance tests.
|
|
class Config
|
|
attr_reader :vagrant_path
|
|
attr_reader :vagrant_version
|
|
attr_reader :env
|
|
attr_reader :boxes
|
|
|
|
def initialize(path)
|
|
@logger = Log4r::Logger.new("acceptance::config")
|
|
@logger.info("Loading configuration from: #{path}")
|
|
options = YAML.load_file(path)
|
|
@logger.info("Loaded: #{options.inspect}")
|
|
|
|
@vagrant_path = options["vagrant_path"]
|
|
@vagrant_version = options["vagrant_version"]
|
|
@env = options["env"]
|
|
@boxes = options["boxes"]
|
|
|
|
# Verify the configuration object.
|
|
validate
|
|
end
|
|
|
|
# This method verifies the configuration and makes sure that
|
|
# all the configuration is available and appears good. This
|
|
# method will raise an ArgumentError in the case that anything
|
|
# is wrong.
|
|
def validate
|
|
if !@vagrant_path || !File.file?(@vagrant_path)
|
|
raise ArgumentError, "'vagrant_path' must point to the `vagrant` executable"
|
|
elsif !@vagrant_version
|
|
raise ArgumentError, "`vagrant_version' must be set to the version of the `vagrant` executable"
|
|
end
|
|
|
|
if !@boxes || !@boxes.is_a?(Hash)
|
|
raise ArgumentError, "`boxes` must be a dictionary of available boxes on the local filesystem."
|
|
end
|
|
end
|
|
end
|
|
end
|