News for hackers. Stuff that matters.
Re:Support for Test-Driven Devops by makerops on Friday January 17, 2014 @10:29AM (#7076224)
It doesn't always though, with chef/puppet et al, you can write the code to throw up X (aapche w/ ssl etc), but unless you use a testing facility, there is no way to know for sure (other than manually checking obviously).
Re:Support for Test-Driven Devops by falcolas on Friday January 17, 2014 @12:06PM (#7076887)
You can dictate that a service is running, and it will ensure that the service is running. You can also set up more advanced HTML checks in at least some frameworks[1] to ensure that the contents are being served correctly.

[1] http://docs.ansible.com/get_url_module.html & http://docs.ansible.com/uri_module.html for ansible, I'm fairly certain you can build up something similar for puppet and chef, though I haven't done it myself.

Re:Support for Test-Driven Devops by sandfox on Saturday January 18, 2014 @08:32AM (#7080945)
Writing code/recipes/etc for chef/ansible/puppet is no different to writing code for an application. Just because you think you have dictated (in code) that things should be a certain way does not mean that what will be executed or run.
Re:Support for Test-Driven Devops by falcolas on Saturday January 18, 2014 @08:49AM (#7080986)
The exact same caveats could be applied to unit testing an environment. Common sense and practical tests rule any form of automation.