ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Update test_strategies.rst

Browse source 
Changed unit tests to unit test for the singular playbook...
This commit is contained in:
Adam Morris 2014-05-27 10:54:14 -07:00
parent 30ac368d5c
commit 6c9cb5de87
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docsite/rst/test_strategies.rst
View file

@ -240,7 +240,7 @@ as part of a Continous Integration/Continous Delivery pipeline, as is covered in
The focus should not be on infrastructure testing, but on application testing, so we strongly encourage getting together with your
QA team and ask what sort of tests would make sense to run every time you deploy development VMs, and which sort of tests they would like
to run against the stage environment on every deploy. Obviously at the development stage, unit tests are great too. But don't unit
tests your playbook. Ansible describes states of resources declaratively, so you don't have to. If there are cases where you want
test your playbook. Ansible describes states of resources declaratively, so you don't have to. If there are cases where you want
to be sure of something though, that's great, and things like stat/assert are great go-to modules for that purpose.
In all, testing is a very organizational and site-specific thing. Everybody should be doing it, but what makes the most sense for your