As part of an effort to improve the overall stability of MW-Vagrant, we should establish decent unit-test coverage for the plugin classes/modules using rspec and possibly [[ https://github.com/mitchellh/vagrant-spec | vagrant-spec ]]. Good baseline coverage (and continuing coverage) will protect against regression during development of new features, fixes, and refactoring.
The test suite should be easily runnable by developers before pushing commits and runnable by CI before merges using `bundle exec rspec`. It may make sense to keep unit tests separate from any functional/acceptance tests we might develop, so as not to muddle the utility of each.
It might also be a good idea to include measurement of coverage with something like [[ https://github.com/colszowka/simplecov | simplecov ]], not so much to measure the absolute health of the project but to measure changes over time—awareness of an incline/decline in coverage will help promote TDD.