-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add integration/acceptance tests #3
Comments
@tmatilai Sorry, I've completely forgot about this :P So I've been thinking about using Bats for that kind of stuff but I haven't tried anything yet. The idea would be to fire up a VBox VM and run Bats tests against a vagrant-lxc VM to check for the expected behavior. BTW, on vagrant-lxc itself I'm doing some sanity checks using vagrant internals but I'm not sure that is the best approach and some people might even consider it an integration test rather than acceptance. |
@fgrehm no probs. I'm visiting Finland/Europe for a month and it seems I don't have time for OSS projects at all. :/ I've used Bats with Test Kitchen and it's nice and simple. Actually I have been thinking that the Test Kitchen itself could be really good fit for all this, at least when the Chef dependency is removed. With it we could spin up the VMs in parallel and run bats (or what ever) test suites on them. |
@tmatilai no worries! free to ping me once you get to this ;) |
Would be great to have some automated way of testing that the plugin is working as expected. At least to verify that the generated configuration matches expectations, but maybe even trying to validate that it has the wanted effect.
The text was updated successfully, but these errors were encountered: