You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2019. It is now read-only.
After an OS has been installed on your VM image, you can verify that the machine is configured as intended with the validate subcommand. Veewee provides several tests to help you with that. The tests are located under the validation/ directory.
This subcommand executes all tests on a given machine:
$ bundle exec veewee vbox validate 'sles12'
Validate will run some cucumber tests against the box to see if it has the necessary bits and pieces (e.g. for vagrant to work).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After an OS has been installed on your VM image, you can verify that the machine is configured as intended with the validate subcommand. Veewee provides several tests to help you with that. The tests are located under the validation/ directory.
This subcommand executes all tests on a given machine:
Validate will run some cucumber tests against the box to see if it has the necessary bits and pieces (e.g. for vagrant to work).
The text was updated successfully, but these errors were encountered: