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.
37 lines
1.2 KiB
Ruby
37 lines
1.2 KiB
Ruby
require File.expand_path("../base", __FILE__)
|
|
|
|
describe "vagrant init" do
|
|
include_context "acceptance"
|
|
|
|
it "creates a Vagrantfile in the working directory" do
|
|
vagrantfile = environment.workdir.join("Vagrantfile")
|
|
assert(!vagrantfile.exist?, "Vagrantfile shouldn't exist")
|
|
|
|
result = execute("vagrant", "init")
|
|
assert(result.success?, "init should succeed")
|
|
assert(vagrantfile.exist?, "Vagrantfile should exist")
|
|
end
|
|
|
|
it "creates a Vagrantfile with the box set to the given argument" do
|
|
vagrantfile = environment.workdir.join("Vagrantfile")
|
|
|
|
result = execute("vagrant", "init", "foo")
|
|
assert(result.success?, "init should succeed")
|
|
assert(vagrantfile.read =~ /config.vm.box = "foo"$/,
|
|
"config.vm.box should be set to 'foo'")
|
|
end
|
|
|
|
it "creates a Vagrantfile with the box URL set to the given argument" do
|
|
vagrantfile = environment.workdir.join("Vagrantfile")
|
|
|
|
result = execute("vagrant", "init", "foo", "bar")
|
|
assert(result.success?, "init should succeed")
|
|
|
|
contents = vagrantfile.read
|
|
assert(contents =~ /config.vm.box = "foo"$/,
|
|
"config.vm.box should be set to 'foo'")
|
|
assert(contents =~ /config.vm.box_url = "bar"$/,
|
|
"config.vm.box_url should be set to 'bar'")
|
|
end
|
|
end
|