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
See #3 how i found this issue
I am not sure if thats by design or not
But my expectations from this plugin is to be used once vagrant up finished to create the VM
So i will bring the VM up , and only then run the rspec tests with vagrant rspec
The text was updated successfully, but these errors were encountered:
no , as far as i see , its only verifying the setup (it crashed for missing spec folder)
I agree that there is a slim chance you install a plugin and don't have the setup for it in place
but that was my experience, and simply installing this plugin made my vagrant to stop working
So one option is to only do validation when user calls vagrant rspec
Or maybe the only thing needed here is some more documentation
Hrm, and all it's doing is looking for a directory. If the dir doesn't exist, a reasonable thing to do might be to create it, instead of erroring. What do you think?
And I agree, the directory structure should be documented more clearly.
See #3 how i found this issue
I am not sure if thats by design or not
But my expectations from this plugin is to be used once vagrant up finished to create the VM
So i will bring the VM up , and only then run the rspec tests with vagrant rspec
The text was updated successfully, but these errors were encountered: