vagrant-unbundled 1.9.5.1 → 1.9.7.1

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-spec-9bba7e122837/.gitignore

@@ -1,18 +0,0 @@
-.DS_Store
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-local_config.rb
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-vagrant-spec.config.rb

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-spec-9bba7e122837/.travis.yml

@@ -1,8 +0,0 @@
-sudo: false
-language: ruby
-rvm:
-    - 2.0.0
-env:
-  global:
-    - NOKOGIRI_USE_SYSTEM_LIBRARIES=true
-script: bundle exec rspec

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-spec-9bba7e122837/Gemfile

@@ -1,5 +0,0 @@
-source 'https://rubygems.org'
-
-gemspec
-
-gem "vagrant", git: "https://github.com/mitchellh/vagrant.git"

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-spec-9bba7e122837/LICENSE.txt

@@ -1,373 +0,0 @@
-Mozilla Public License Version 2.0
-==================================
-
-1. Definitions
---------------
-
-1.1. "Contributor"
-    means each individual or legal entity that creates, contributes to
-    the creation of, or owns Covered Software.
-
-1.2. "Contributor Version"
-    means the combination of the Contributions of others (if any) used
-    by a Contributor and that particular Contributor's Contribution.
-
-1.3. "Contribution"
-    means Covered Software of a particular Contributor.
-
-1.4. "Covered Software"
-    means Source Code Form to which the initial Contributor has attached
-    the notice in Exhibit A, the Executable Form of such Source Code
-    Form, and Modifications of such Source Code Form, in each case
-    including portions thereof.
-
-1.5. "Incompatible With Secondary Licenses"
-    means
-
-    (a) that the initial Contributor has attached the notice described
-        in Exhibit B to the Covered Software; or
-
-    (b) that the Covered Software was made available under the terms of
-        version 1.1 or earlier of the License, but not also under the
-        terms of a Secondary License.
-
-1.6. "Executable Form"
-    means any form of the work other than Source Code Form.
-
-1.7. "Larger Work"
-    means a work that combines Covered Software with other material, in
-    a separate file or files, that is not Covered Software.
-
-1.8. "License"
-    means this document.
-
-1.9. "Licensable"
-    means having the right to grant, to the maximum extent possible,
-    whether at the time of the initial grant or subsequently, any and
-    all of the rights conveyed by this License.
-
-1.10. "Modifications"
-    means any of the following:
-
-    (a) any file in Source Code Form that results from an addition to,
-        deletion from, or modification of the contents of Covered
-        Software; or
-
-    (b) any new file in Source Code Form that contains any Covered
-        Software.
-
-1.11. "Patent Claims" of a Contributor
-    means any patent claim(s), including without limitation, method,
-    process, and apparatus claims, in any patent Licensable by such
-    Contributor that would be infringed, but for the grant of the
-    License, by the making, using, selling, offering for sale, having
-    made, import, or transfer of either its Contributions or its
-    Contributor Version.
-
-1.12. "Secondary License"
-    means either the GNU General Public License, Version 2.0, the GNU
-    Lesser General Public License, Version 2.1, the GNU Affero General
-    Public License, Version 3.0, or any later versions of those
-    licenses.
-
-1.13. "Source Code Form"
-    means the form of the work preferred for making modifications.
-
-1.14. "You" (or "Your")
-    means an individual or a legal entity exercising rights under this
-    License. For legal entities, "You" includes any entity that
-    controls, is controlled by, or is under common control with You. For
-    purposes of this definition, "control" means (a) the power, direct
-    or indirect, to cause the direction or management of such entity,
-    whether by contract or otherwise, or (b) ownership of more than
-    fifty percent (50%) of the outstanding shares or beneficial
-    ownership of such entity.
-
-2. License Grants and Conditions
---------------------------------
-
-2.1. Grants
-
-Each Contributor hereby grants You a world-wide, royalty-free,
-non-exclusive license:
-
-(a) under intellectual property rights (other than patent or trademark)
-    Licensable by such Contributor to use, reproduce, make available,
-    modify, display, perform, distribute, and otherwise exploit its
-    Contributions, either on an unmodified basis, with Modifications, or
-    as part of a Larger Work; and
-
-(b) under Patent Claims of such Contributor to make, use, sell, offer
-    for sale, have made, import, and otherwise transfer either its
-    Contributions or its Contributor Version.
-
-2.2. Effective Date
-
-The licenses granted in Section 2.1 with respect to any Contribution
-become effective for each Contribution on the date the Contributor first
-distributes such Contribution.
-
-2.3. Limitations on Grant Scope
-
-The licenses granted in this Section 2 are the only rights granted under
-this License. No additional rights or licenses will be implied from the
-distribution or licensing of Covered Software under this License.
-Notwithstanding Section 2.1(b) above, no patent license is granted by a
-Contributor:
-
-(a) for any code that a Contributor has removed from Covered Software;
-    or
-
-(b) for infringements caused by: (i) Your and any other third party's
-    modifications of Covered Software, or (ii) the combination of its
-    Contributions with other software (except as part of its Contributor
-    Version); or
-
-(c) under Patent Claims infringed by Covered Software in the absence of
-    its Contributions.
-
-This License does not grant any rights in the trademarks, service marks,
-or logos of any Contributor (except as may be necessary to comply with
-the notice requirements in Section 3.4).
-
-2.4. Subsequent Licenses
-
-No Contributor makes additional grants as a result of Your choice to
-distribute the Covered Software under a subsequent version of this
-License (see Section 10.2) or under the terms of a Secondary License (if
-permitted under the terms of Section 3.3).
-
-2.5. Representation
-
-Each Contributor represents that the Contributor believes its
-Contributions are its original creation(s) or it has sufficient rights
-to grant the rights to its Contributions conveyed by this License.
-
-2.6. Fair Use
-
-This License is not intended to limit any rights You have under
-applicable copyright doctrines of fair use, fair dealing, or other
-equivalents.
-
-2.7. Conditions
-
-Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
-in Section 2.1.
-
-3. Responsibilities
--------------------
-
-3.1. Distribution of Source Form
-
-All distribution of Covered Software in Source Code Form, including any
-Modifications that You create or to which You contribute, must be under
-the terms of this License. You must inform recipients that the Source
-Code Form of the Covered Software is governed by the terms of this
-License, and how they can obtain a copy of this License. You may not
-attempt to alter or restrict the recipients' rights in the Source Code
-Form.
-
-3.2. Distribution of Executable Form
-
-If You distribute Covered Software in Executable Form then:
-
-(a) such Covered Software must also be made available in Source Code
-    Form, as described in Section 3.1, and You must inform recipients of
-    the Executable Form how they can obtain a copy of such Source Code
-    Form by reasonable means in a timely manner, at a charge no more
-    than the cost of distribution to the recipient; and
-
-(b) You may distribute such Executable Form under the terms of this
-    License, or sublicense it under different terms, provided that the
-    license for the Executable Form does not attempt to limit or alter
-    the recipients' rights in the Source Code Form under this License.
-
-3.3. Distribution of a Larger Work
-
-You may create and distribute a Larger Work under terms of Your choice,
-provided that You also comply with the requirements of this License for
-the Covered Software. If the Larger Work is a combination of Covered
-Software with a work governed by one or more Secondary Licenses, and the
-Covered Software is not Incompatible With Secondary Licenses, this
-License permits You to additionally distribute such Covered Software
-under the terms of such Secondary License(s), so that the recipient of
-the Larger Work may, at their option, further distribute the Covered
-Software under the terms of either this License or such Secondary
-License(s).
-
-3.4. Notices
-
-You may not remove or alter the substance of any license notices
-(including copyright notices, patent notices, disclaimers of warranty,
-or limitations of liability) contained within the Source Code Form of
-the Covered Software, except that You may alter any license notices to
-the extent required to remedy known factual inaccuracies.
-
-3.5. Application of Additional Terms
-
-You may choose to offer, and to charge a fee for, warranty, support,
-indemnity or liability obligations to one or more recipients of Covered
-Software. However, You may do so only on Your own behalf, and not on
-behalf of any Contributor. You must make it absolutely clear that any
-such warranty, support, indemnity, or liability obligation is offered by
-You alone, and You hereby agree to indemnify every Contributor for any
-liability incurred by such Contributor as a result of warranty, support,
-indemnity or liability terms You offer. You may include additional
-disclaimers of warranty and limitations of liability specific to any
-jurisdiction.
-
-4. Inability to Comply Due to Statute or Regulation
----------------------------------------------------
-
-If it is impossible for You to comply with any of the terms of this
-License with respect to some or all of the Covered Software due to
-statute, judicial order, or regulation then You must: (a) comply with
-the terms of this License to the maximum extent possible; and (b)
-describe the limitations and the code they affect. Such description must
-be placed in a text file included with all distributions of the Covered
-Software under this License. Except to the extent prohibited by statute
-or regulation, such description must be sufficiently detailed for a
-recipient of ordinary skill to be able to understand it.
-
-5. Termination
---------------
-
-5.1. The rights granted under this License will terminate automatically
-if You fail to comply with any of its terms. However, if You become
-compliant, then the rights granted under this License from a particular
-Contributor are reinstated (a) provisionally, unless and until such
-Contributor explicitly and finally terminates Your grants, and (b) on an
-ongoing basis, if such Contributor fails to notify You of the
-non-compliance by some reasonable means prior to 60 days after You have
-come back into compliance. Moreover, Your grants from a particular
-Contributor are reinstated on an ongoing basis if such Contributor
-notifies You of the non-compliance by some reasonable means, this is the
-first time You have received notice of non-compliance with this License
-from such Contributor, and You become compliant prior to 30 days after
-Your receipt of the notice.
-
-5.2. If You initiate litigation against any entity by asserting a patent
-infringement claim (excluding declaratory judgment actions,
-counter-claims, and cross-claims) alleging that a Contributor Version
-directly or indirectly infringes any patent, then the rights granted to
-You by any and all Contributors for the Covered Software under Section
-2.1 of this License shall terminate.
-
-5.3. In the event of termination under Sections 5.1 or 5.2 above, all
-end user license agreements (excluding distributors and resellers) which
-have been validly granted by You or Your distributors under this License
-prior to termination shall survive termination.
-
-************************************************************************
-*                                                                      *
-*  6. Disclaimer of Warranty                                           *
-*  -------------------------                                           *
-*                                                                      *
-*  Covered Software is provided under this License on an "as is"       *
-*  basis, without warranty of any kind, either expressed, implied, or  *
-*  statutory, including, without limitation, warranties that the       *
-*  Covered Software is free of defects, merchantable, fit for a        *
-*  particular purpose or non-infringing. The entire risk as to the     *
-*  quality and performance of the Covered Software is with You.        *
-*  Should any Covered Software prove defective in any respect, You     *
-*  (not any Contributor) assume the cost of any necessary servicing,   *
-*  repair, or correction. This disclaimer of warranty constitutes an   *
-*  essential part of this License. No use of any Covered Software is   *
-*  authorized under this License except under this disclaimer.         *
-*                                                                      *
-************************************************************************
-
-************************************************************************
-*                                                                      *
-*  7. Limitation of Liability                                          *
-*  --------------------------                                          *
-*                                                                      *
-*  Under no circumstances and under no legal theory, whether tort      *
-*  (including negligence), contract, or otherwise, shall any           *
-*  Contributor, or anyone who distributes Covered Software as          *
-*  permitted above, be liable to You for any direct, indirect,         *
-*  special, incidental, or consequential damages of any character      *
-*  including, without limitation, damages for lost profits, loss of    *
-*  goodwill, work stoppage, computer failure or malfunction, or any    *
-*  and all other commercial damages or losses, even if such party      *
-*  shall have been informed of the possibility of such damages. This   *
-*  limitation of liability shall not apply to liability for death or   *
-*  personal injury resulting from such party's negligence to the       *
-*  extent applicable law prohibits such limitation. Some               *
-*  jurisdictions do not allow the exclusion or limitation of           *
-*  incidental or consequential damages, so this exclusion and          *
-*  limitation may not apply to You.                                    *
-*                                                                      *
-************************************************************************
-
-8. Litigation
--------------
-
-Any litigation relating to this License may be brought only in the
-courts of a jurisdiction where the defendant maintains its principal
-place of business and such litigation shall be governed by laws of that
-jurisdiction, without reference to its conflict-of-law provisions.
-Nothing in this Section shall prevent a party's ability to bring
-cross-claims or counter-claims.
-
-9. Miscellaneous
-----------------
-
-This License represents the complete agreement concerning the subject
-matter hereof. If any provision of this License is held to be
-unenforceable, such provision shall be reformed only to the extent
-necessary to make it enforceable. Any law or regulation which provides
-that the language of a contract shall be construed against the drafter
-shall not be used to construe this License against a Contributor.
-
-10. Versions of the License
----------------------------
-
-10.1. New Versions
-
-Mozilla Foundation is the license steward. Except as provided in Section
-10.3, no one other than the license steward has the right to modify or
-publish new versions of this License. Each version will be given a
-distinguishing version number.
-
-10.2. Effect of New Versions
-
-You may distribute the Covered Software under the terms of the version
-of the License under which You originally received the Covered Software,
-or under the terms of any subsequent version published by the license
-steward.
-
-10.3. Modified Versions
-
-If you create software not governed by this License, and you want to
-create a new license for such software, you may create and use a
-modified version of this License if you rename the license and remove
-any references to the name of the license steward (except to note that
-such modified license differs from this License).
-
-10.4. Distributing Source Code Form that is Incompatible With Secondary
-Licenses
-
-If You choose to distribute Source Code Form that is Incompatible With
-Secondary Licenses under the terms of this version of the License, the
-notice described in Exhibit B of this License must be attached.
-
-Exhibit A - Source Code Form License Notice
--------------------------------------------
-
-  This Source Code Form is subject to the terms of the Mozilla Public
-  License, v. 2.0. If a copy of the MPL was not distributed with this
-  file, You can obtain one at http://mozilla.org/MPL/2.0/.
-
-If it is not possible or desirable to put the notice in a particular
-file, then You may include the notice in a location (such as a LICENSE
-file in a relevant directory) where a recipient would be likely to look
-for such a notice.
-
-You may add additional accurate notices of copyright ownership.
-
-Exhibit B - "Incompatible With Secondary Licenses" Notice
----------------------------------------------------------
-
-  This Source Code Form is "Incompatible With Secondary Licenses", as
-  defined by the Mozilla Public License, v. 2.0.

data/vendor/bundle/ruby/2.4.0/bundler/gems/vagrant-spec-9bba7e122837/README.md

@@ -1,319 +0,0 @@
-# Vagrant Spec
-
-**Work-in-progress:** This library is not ready for general use yet and
-is under active development. The documentation will become much better once
-this is more easily usable.
-
-`vagrant-spec` is a both a specification of how Vagrant and its various
-components should behave as well as a library of testing helpers that
-let you write your own unit and acceptance tests for Vagrant.
-
-The library provides a set of helper methods in addition to
-[RSpec](https://github.com/rspec/rspec) matchers and expectations to help
-you both unit test and acceptance test Vagrant components. The RSpec
-components are built on top of the helper methods so that the test library
-can be used with your test framework of choice, but the entire tool is
-geared very heavily towards RSpec.
-
-**Table of Contents**
-
-- [Prerequisites](#prerequisites)
-- [Installation](#installation)
-	- [Standalone](#standalone)
-	- [Plugin Development Environment](#plugin-development-environment)
-- [Running Acceptance Tests](#running-acceptance-tests)
-	- [Configuration](#configuration)
-	- [Running](#running)
-	- [Provider's Acceptance Specs](#provider-s-acceptance-specs)
-- [Writing Acceptance Tests](#writing-acceptance-tests)
-	- [Configuring Component Paths](#configuring-component-paths)
-	- [Standalone Components](#standalone-components)
-	- [Provider Parameterized Components](#provider-parameterized-components)
-	- [Helpers](#helpers)
-		- [Context: "acceptance"](#context-acceptance)
-		- [Matcher: "exit_with"](#matcher-exit_with)
-
-## Prerequisites
-
- * Ruby 2.0.0 or greater
-
-## Installation
-
-### Standalone
-
-`vagrant-spec` can be installed as a standalone tool to black-box test
-existing Vagrant installations (potentially with a combination of plugins).
-**Vagrant plugin developers** should see the next section
-"Plugin Development Environment" to see the proper way to test plugins
-in development.
-
-To install `vagrant-spec` as a standalone tool, simply gem install it:
-
-```
-$ gem build vagrant-spec.gemspec
-$ gem install vagrant-spec
-```
-
-### Plugin Development Environment
-
-If you're developing a Vagrant plugin and wish to use `vagrant-spec`
-to help test that plugin, then you should add `vagrant-spec` as a
-development dependency to your plugin by modifying the gemspec.
-
-The version of `vagrant-spec` follows the version of Vagrant.
-So if you're writing your plugin to target Vagrant 1.4, then you
-should constrain the plugin to that version:
-
-```
-spec.add_development_dependency "vagrant-spec", "~> 1.4.0"
-```
-
-If you want to use the latest (from git) of `vagrant-spec`, you
-should add the git dependency to your `Gemfile`:
-
-```
-gem 'vagrant-spec', git: "https://github.com/mitchellh/vagrant-spec.git"
-```
-
-`vagrant-spec` can then be executed by being prefixed with
-`bundle exec`. Since your Gemfile should also contain "vagrant",
-vagrant-spec can then execute Vagrant in the context of the bundler
-environment in order to test your plugin.
-
-## Running Acceptance Tests
-
-This section documents how acceptance tests can be configured, run, and
-written. Acceptance tests test Vagrant as a black box: they configure some
-Vagrant environment (by creating a Vagrantfile and perhaps other files),
-execute Vagrant, and assert some sort of result. They have _zero_ access
-to the code internals.
-
-`vagrant-spec` contains a set of acceptance tests that can easily verify
-the behavior of Vagrant. It also provides a framework for writing new
-acceptance tests that can easily be executed in the context of Vagrant.
-
-### Configuration
-
-Before running the acceptance tests, you must first configure
-`vagrant-spec.` Configuration is done by creating the file
-`vagrant-spec.config.rb`. It looks like the following:
-
-```ruby
-Vagrant::Spec::Acceptance.configure do |c|
-  # ...
-end
-```
-
-The available options for `c` and their defaults are fully documented
-in [the configuration source file](https://github.com/mitchellh/vagrant-spec/blob/master/lib/vagrant-spec/acceptance/configuration.rb). Please read through the documentation thoroughly and
-implement what you need.
-
-### Running
-
-Running the full suite of acceptance tests can be horribly long.
-It is recommended you only run a component at a time (or a handful
-of components). To view the list of testable components based on
-your configuration, run `vagrant-spec components`. You might
-see something like the following:
-
-```
-$ vagrant-spec components
-cli
-provider/virtualbox/basic
-provider/virtualbox/provisioner/shell
-provider/virtualbox/synced_folder
-```
-
-Choose a component to run, and run it:
-
-```
-$ vagrant-spec test --components cli
-...
-```
-
-That component will be tested.
-
-### Provider's Acceptance Specs
-
-`vagrant-spec` ships with a handful of [provider acceptance tests](acceptance/provider)
-used to test Vagrant's built in VirtualBox provider that you can reuse
-to test your custom plugins.
-
-All that it needs is the following block on your `vagrant-spec.config.rb`:
-
-```ruby
-Vagrant::Spec::Acceptance.configure do |c|
-  # ... other stuff ...
-  c.provider 'foobar', box: '<PATH TO A BOX>'
-end
-```
-
-With that in place, you should be able to run provider's components with
-`vagrant-spec test`. For the complete list, please run `vagrant-spec components`.
-
-_The code example might get outdated while we don't have a stable release,
-please refer to [Vagrant's configuration](https://github.com/mitchellh/vagrant/blob/master/vagrant-spec.config.example.rb)
-in case things are not working for you_
-
-## Writing Acceptance Tests
-
-In addition to running the tests that already exist, `vagrant-spec`
-makes it trivial to write new acceptance tests. This is especially
-useful if you're writing your own plugin.
-
-All new tests must go within their own folder in your project.
-For the sake of these docs, put your tests in the `vagrant-spec`
-folder.
-
-### Configuring Component Paths
-
-For `vagrant-spec` to know about new tests you write, you must
-add the path that will hold the Ruby files to the configuration
-"component_paths". These are the paths where the tests are
-automatically loaded from by `vagrant-spec`. Example:
-
-```ruby
-Vagrant::Spec::Acceptance.configure do |c|
-  c.component_paths << "vagrant-spec"
-end
-```
-
-Within the component paths, any files matching `*_{output,spec}.rb` within
-any directory are loaded. Components are found based on the "component"
-key as shown in the sections below.
-
-If the path is relative, it will be relative to the pwd when
-`vagrant-spec` is executed.
-
-### Standalone Components
-
-If your plugin doesn't depend on a specific provider, then it is
-known as a _component_ (specifically a standalone one) of
-`vagrant-spec.` Create a new file in the `vagrant-spec` folder
-of your project with something that looks like the following:
-
-```ruby
-describe "my test", component: "my-test" do
-  include_context "acceptance"
-
-  it "can output the version" do
-    expect(execute("vagrant", "-v")).to exit_with(0)
-  end
-end
-```
-
-This should be fairly straightforward RSpec code. The key
-things are:
-
-* `component: "my-test"` in the describe definition. This is read
-  by `vagrant-spec` and will be what is outputted in by
-  `vagrant-spec components`. Set this to something unique. The actual
-  name of the describe block (in this case "my test") doesn't matter
-  except for output.
-
-* `include_context "acceptance"` exposes important helpers such
-  as the `execute` method used. These helpers allow you to execute
-  Vagrant in a completely isolated environment so it doesn't mess up
-  any actual Vagrant state that may be setup on your computer.
-
-And that's it for writing a custom component. You should be able to
-see it when you run `vagrant-spec components` and you should also
-be able to run it.
-
-### Provider Parameterized Components
-
-Tests that require a provider (basically any test that executes
-`vagrant up`) are known as provider parameterized components. They
-will be executed for every provider under test.
-
-These are useful, for example, for provisioners. Provisioners should
-work regardless of what provider is running them. Therefore, if you're
-testing VirtualBox and VMware, you want to be sure that the "shell"
-provisioner works, for example.
-
-Provider parameterized components are implemented as RSpec
-shared examples:
-
-```ruby
-shared_examples "provider/foo" do |provider, options|
-  it "does things" do
-    puts "Executing for provider: #{provider}"
-  end
-end
-```
-
-The key things in this are:
-
-* The `provider/` prefix in the name of the shared example group.
-  `vagrant-spec` treats this specially as a provider parameterized
-  component. A new component will automatically be created by
-  `vagrant-spec` for every provider.
-
-* The `|provider, options|` parameters to the shared example group.
-  Parameterized components are, as they're named, parameterized.
-  The two parameters they receive are the provider under test
-  as well as any options for that provider.
-
-If you have `vagrant-spec` configured to test a provider, then when
-you run `vagrant-spec components`, you should see your component
-listed:
-
-```
-$ vagrant-spec components
-...
-provider/virtualbox/foo
-...
-```
-
-And you can now run the tests!
-
-### Helpers
-
-#### Context: "acceptance"
-
-The "acceptance" context defines many helpers for executing
-Vagrant within an isolated environment and setting up that
-environment. [See the context source file for detailed docs](https://github.com/mitchellh/vagrant-spec/blob/master/lib/vagrant-spec/acceptance/rspec/context.rb).
-
-The key features of the context are:
-
-* `execute` is a method for executing commands within the
-  isolated environment. The isolated environment prepares a
-  empty working directory as well as changes the home directory
-  from the point-of-view of executing processes.
-
-* `environment` is the actual instance of the "IsolatedEnvironment"
-  class. It most importantly allows for skeletons to be used to
-  create complex directory setups. [See the IsolatedEnvironment source for more docs.](https://github.com/mitchellh/vagrant-spec/blob/master/lib/vagrant-spec/acceptance/isolated_environment.rb)
-
-#### Matcher: "exit_with"
-
-This matcher can be used to test that a command executed with
-`execute` exited with a good exit status. If it didn't, this matcher
-will produce helpful output containing the stdout/stderr of the
-command:
-
-```ruby
-result = execute("vagrant", "up")
-expect(result).to exit_with(0)
-```
-
-Although, a shortcut for this pattern is `assert_execute`:
-
-```ruby
-assert_execute("vagrant", "up")
-````
-
-## Writing Unit Tests
-
-In addition to having a full acceptance test suite, `vagrant-spec` contains
-helpers that can be used to helper unit test plugins for Vagrant. These unit
-test helpers are test framework agnostic but there are also some helpers
-for rspec if you use that.
-
-To use the unit tests helpers, just load `vagrant-spec/unit` somewhere early
-in your test files:
-
-```ruby
-require "vagrant-spec/unit"
-```