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

Add automated tests #3

Open
geerlingguy opened this issue Feb 22, 2020 · 4 comments
Open

Add automated tests #3

geerlingguy opened this issue Feb 22, 2020 · 4 comments
Labels

Comments

@geerlingguy
Copy link
Owner

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.

@geerlingguy
Copy link
Owner Author

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

@stale
Copy link

stale bot commented May 22, 2020

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.

@stale stale bot added the stale label May 22, 2020
@stale
Copy link

stale bot commented May 22, 2020

This issue is no longer marked for closure.

@stale stale bot removed the stale label May 22, 2020
@gotmax23
Copy link

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 requirements.yml file).

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

No branches or pull requests

2 participants