exactly. this is particularly important if you ever rely on 3rd party modules. a common pattern is to spin up VMs, apply config management, then validate config management as part of your infrastructure's ci process.
...you run goss during the process of developing your ansible roles. Ansible roles are code. Goss allows you to test that code well before you're attempting to create real systems. Real systems include dev/acceptance…
That sounds a lot like "if my code is bad, I'll find out when it breaks in production, so why test?". Tests allow you to make changes to your ansible configs, then test that the ansible config works correctly before you…
https://github.com/przemyslawpluta/node-youtube-dl/blob/mast... except for those times it downloads a youtube-dl binary. https://github.com/przemyslawpluta/node-youtube-dl/blob/mast...
For the same reason you write unit or integration tests.
exactly. this is particularly important if you ever rely on 3rd party modules. a common pattern is to spin up VMs, apply config management, then validate config management as part of your infrastructure's ci process.
...you run goss during the process of developing your ansible roles. Ansible roles are code. Goss allows you to test that code well before you're attempting to create real systems. Real systems include dev/acceptance…
That sounds a lot like "if my code is bad, I'll find out when it breaks in production, so why test?". Tests allow you to make changes to your ansible configs, then test that the ansible config works correctly before you…
https://github.com/przemyslawpluta/node-youtube-dl/blob/mast... except for those times it downloads a youtube-dl binary. https://github.com/przemyslawpluta/node-youtube-dl/blob/mast...
For the same reason you write unit or integration tests.