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

Test Tooling #4

Open
ChrisMcKenzie opened this issue Oct 10, 2016 · 0 comments
Open

Test Tooling #4

ChrisMcKenzie opened this issue Oct 10, 2016 · 0 comments

Comments

@ChrisMcKenzie
Copy link
Owner

ChrisMcKenzie commented Oct 10, 2016

One thing I think that is lacking in most CM tools is a testing framework I think this should be an import part of preflight. My thinking is that testing should follow a convention much like how golang achieves testing, in which tests are place in a file with the same name as the module it tests suffixed with _test.pf

I haven't spent to much time on the DSL for testing yet but I imagine something like the following.

my_module_test.pf

assert "homebrew" "has_vim_installed" {
  version = ">=8.0.0"
}

assert "file" "contains_templated_settings" {
  value = "${data.file.vimrc.rendered}"
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant