haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
vagrant/test/unit/base.rb

31 lines
815 B
Ruby
Raw Normal View History

Environment UI class can now be set through the environment init
2011-12-04 00:07:34 +00:00
require "rubygems"
require "rspec/autorun"
# Require Vagrant itself so we can reference the proper
# classes to test.
require "vagrant"
Clean up test load paths
2011-12-11 23:53:11 +00:00
# Add the test directory to the load path
VM-specific configuration now works.
2011-12-04 03:05:50 +00:00
$:.unshift File.expand_path("../../", __FILE__)
Introduce Config::Loader Config::Loader will be the new class responsible for loading configuration and replaces the previous dual-role "Vagrant::Config" played. While this commit is very early-stage, once this new architecture is flushed out, it will make loading, using, and extending configuration much easier and cleaner. Additionally, I believe this will help post Vagrant 1.0 if multi-language configuration is implemented.
2011-12-04 01:12:48 +00:00
# Load in helpers
Use a temporary directory for the VAGRANT_CWD when running tests Tests before were picking up a Vagrantfile in the Vagrant source directory, which can cause some funny failures. This ensures that each test run will actually establish a new temporary CWD so that a Vagrantfile is hopefully never found.
2012-06-24 06:56:39 +00:00
require "support/tempdir"
refactoring ubuntu/debian change_host_name there's been a lot of churn around this code, so i figure it was worth trying to clean it up. - the methods were doing a lot, so make them into template methods with one helper per step - spread out /etc/hosts regexp into a couple of helper variables for clarity - remove handling for broken hostname implementations (like basing all of the checks on name.split('.')[0]), since it seems reasonable to remove code dedicated only to handling broken boxes - DRY up the shared code between debian/ubuntu implementations, which clarifies the differences as well - add unit tests around the behavior; this will help us in the future to separate flaws in our understanding from flaws in implementation - includes a new DummyCommunicator in tests which should be useful in supporting additional unit testing of this kind - manually tested this on squeeze, wheezy, precise, quantal, raring, and saucy successfully. handles the issue in #2333
2013-11-23 23:48:00 +00:00
require "unit/support/dummy_communicator"
Create a "dummy" provider for tests
2012-12-23 04:03:39 +00:00
require "unit/support/dummy_provider"
Clean up test load paths
2011-12-11 23:53:11 +00:00
require "unit/support/shared/base_context"
core: clean up tests for synced folder built-ins
2013-12-04 02:30:59 +00:00
require "unit/support/shared/action_synced_folders_context"
providers/virtualbox: support DHCP interfaces for NFS Previously, we required a host-only interface with a static IP for NFS to work in VirtualBox, because we needed access to the guest's IP in order to properly configure mount commands. After boot, VirtualBox exposes the IP addresses of a guest's network adapters via the "guestproperty" interface. This adds support for reading VirtualBox guest properties to the VirtualBox driver and utilizes that support to prepare NFS settings, which removes the necessity for a static IP for NFS to work. In this commit we also start building out scaffolding for unit testing vbox actions and drivers. Test plan: - Prepare a Vagrantfile with the following: * private network with type: :dhcp * synced folder with nfs: true - Boot a VM from this Vagrantfile using the virtualbox provider - Machine should boot successfully with working synced folder
2013-11-22 18:26:36 +00:00
require "unit/support/shared/virtualbox_context"
Introduce Config::Loader Config::Loader will be the new class responsible for loading configuration and replaces the previous dual-role "Vagrant::Config" played. While this commit is very early-stage, once this new architecture is flushed out, it will make loading, using, and extending configuration much easier and cleaner. Additionally, I believe this will help post Vagrant 1.0 if multi-language configuration is implemented.
2011-12-04 01:12:48 +00:00
Environment UI class can now be set through the environment init
2011-12-04 00:07:34 +00:00
# Do not buffer output
$stdout.sync = true
$stderr.sync = true
# Configure RSpec
RSpec.configure do |c|
c.expect_with :rspec, :stdlib
end
Use a temporary directory for the VAGRANT_CWD when running tests Tests before were picking up a Vagrantfile in the Vagrant source directory, which can cause some funny failures. This ensures that each test run will actually establish a new temporary CWD so that a Vagrantfile is hopefully never found.
2012-06-24 06:56:39 +00:00
# Configure VAGRANT_CWD so that the tests never find an actual
# Vagrantfile anywhere, or at least this minimizes those chances.
ENV["VAGRANT_CWD"] = Tempdir.new.path