I should clarify a bit because it looks like I have given you the wrong impression. I have confidence that the Ansible modules behave as advertised. My experience with them to date has been excellent. The Ansible code is not what I'm trying to test.
What I want to test is that the *administrator *has used Ansible to configure a system in a way that meets the spec. In other words, I want to test that the admin has written a *correct *Ansible script. Writing an Ansible playbook is like writing code. When you write code you have to test it externally. I intend exactly what Michael wrote above: testing outcome not implementation. If I don't test the results of the playbook, how do I know the admin wrote the correct script? --Aaron On Wednesday, December 11, 2013 2:39:34 PM UTC-5, Brian Coca wrote: > > FYI, there are quite a few unit test already that verify that 'the file > module' works as advertised, you can run 'make tests' in an ansible > checkout to get them. There should be no need to do this per playbook. > > not all modules or cases are covered but if you want to add tests at this > level I suggest looking into the 'test' dir in the ansible checkout. > > Do you tests all core java libraries when you deploy a war to tomcat? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
