-
Notifications
You must be signed in to change notification settings - Fork 11
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 automated tests #3
Comments
I know it works with at least one requirements file—Drupal VM's—because I built this playbook after getting frustrated keeping it up to date. See related: geerlingguy/drupal-vm#2013 |
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
This issue is no longer marked for closure. |
I'm not even sure what is the best way to implement automated tests is, because the data that this playbook produces is dynamic (i.e. it changes based on the latest version of the roles in the |
Because, you know, testing is good. If you're going to have one of the worlds most disgusting playbooks, laden with tons of Jinja and Pythonic hacks marked up in YAML... you should probably test it and see just how fragile it is.
The text was updated successfully, but these errors were encountered: