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
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}"
}
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: