On 12/11/13, 10:00 AM, John Dewey wrote:
I too would find it useful to have the ability to “unit test” my tasks. However, I have opted to create a testing playbook [1] which handles integration testing. It is not perfect, but allows for TDD/BDD, and integrate into CI gating. [1] https://github.com/blueboxgroup/ursula/tree/master/playbooks/tests/tasks
So this is testing the product itself. That's cool and interesting, but what I'm really interested in is testing of my playbook changes themselves. Something I can run as a gate check on changes coming into my playbook repository. Syntax checking, referencing the right external files, etc...
-jlk -- 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
