atom feed15 messages in com.madstop.puppet-usersRe: [Puppet-users] What I am doing wi...
FromSent OnAttachments
Julian SimpsonMar 4, 2007 1:49 pm 
Luke KaniesMar 5, 2007 8:57 am 
Thomas LockneyMar 6, 2007 12:31 pm 
Julian SimpsonMar 6, 2007 12:49 pm 
Luke KaniesMar 7, 2007 8:22 am 
Julian SimpsonMar 7, 2007 12:53 pm 
John ArundelMar 7, 2007 1:09 pm 
Luke KaniesMar 7, 2007 1:57 pm 
Luke KaniesMar 7, 2007 1:59 pm 
John ArundelMar 7, 2007 2:26 pm 
Luke KaniesMar 11, 2007 12:53 pm 
Julian SimpsonMar 18, 2007 1:24 pm 
Julian SimpsonMar 18, 2007 1:56 pm 
David SchmittMar 18, 2007 2:36 pm 
Julian SimpsonMar 18, 2007 3:29 pm 
Subject:Re: [Puppet-users] What I am doing with Puppet.
From:Luke Kanies (lu@madstop.com)
Date:Mar 7, 2007 1:57:57 pm
List:com.madstop.puppet-users

On Mar 7, 2007, at 2:53 PM, Julian Simpson wrote:

Like unit tests vs. functional tests in a software project? I agree.

Partially, but also things like testing that a function calls the right function, rather than verifying the whole functional stack.

I've got too much code that tries to verify the whole stack, which means my tests take forever to run (and write) and I have to refactor them all when mid- and bottom-layer functions change.

Behaviour. That's a good word. I want to be able to specify behaviour, and fail if the tests if that behaviour isn't found.

That's tough on both accounts -- you'll need to figure out how to correctly specify behaviour, and then how to test that behaviour. Specification is pretty difficult by itself, but the testing will almost definitely require some kind of external monitoring feedback.

The first step, verifying that your code compiles correctly, is pretty straightforward, and I'd be glad to work with you getting the unit test framework coded up. The second is clearly far more difficult, though, and the only real way I see to do it is via installation on test hosts.

Ok. I'm also happy to focus on the first and mull over the second.

Yeah, I think it's the best place to start.