Skip to content
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

What additional testing makes sense? #16

Open
becw opened this issue Jul 28, 2016 · 2 comments
Open

What additional testing makes sense? #16

becw opened this issue Jul 28, 2016 · 2 comments

Comments

@becw
Copy link
Member

becw commented Jul 28, 2016

Are there crucial or fragile components of the box that we should create tests for?

I'd like a list of these items (probably as separate issues) before proceeding with any development on this issue.

@mathewpeterson
Copy link

One thing that I need to figure out is how to prevent the Vagrantfile from having "provisioners" from being committed.

When I'm doing local testing, I use the Vagrantfile in the drupalbox folder and uncomment the provisioners but if I forget to comment them then they get included in the box template and cause errors for people.

@becw
Copy link
Member Author

becw commented Aug 4, 2016

Ahh, so that's where that error about not being able to find drupalbox.yml comes from. Would it make sense to have a separate Vagrantfile somewhere else in the project for when you're testing changes to the provisioners?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants