Oh, also, you should be able to automate your testing environment using something like Vagrant (http://www.vagrantup.com/), which I've recently found and fallen in love with.
--Matt On Mon, Apr 29, 2013 at 12:13 PM, Matt Simmons < [email protected]> wrote: > Have you looked at Continuous Integration tools like Jenkins ( > http://jenkins-ci.org/)? > > --Matt > > > On Mon, Apr 29, 2013 at 11:54 AM, Atom Powers <[email protected]>wrote: > >> Building on the "infrastructure as code" idea I have been thinking about >> how to write tests for the infrastructure. Service monitoring seems like >> the obvious answer and I am imagining something like a test suite for a >> "development" version of the configuration management system that would be >> used in much the same way as a programmer uses a test suite to make sure >> his program works. >> >> Has anybody done something like this? I imagine the biggest hurdle will >> be setting up the development environment, complete with scratch hosts and >> monitoring that can be reconfigured frequently for those hosts, depending >> on what is being tested. >> >> -- >> Perfection is just a word I use occasionally with mustard. >> --Atom Powers-- >> >> _______________________________________________ >> Discuss mailing list >> [email protected] >> https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss >> This list provided by the League of Professional System Administrators >> http://lopsa.org/ >> >> > > > -- > LITTLE GIRL: But which cookie will you eat FIRST? > COOKIE MONSTER: Me think you have misconception of cookie-eating process. > -- LITTLE GIRL: But which cookie will you eat FIRST? COOKIE MONSTER: Me think you have misconception of cookie-eating process.
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
