for what it's worth:
for a while I was experimenting with cucumber to test scripts running
on linux machines. And yes , IMHO it is the way to go .
It worked well with the behavior testing just a you guys described.
still just as in regular development, bdd can be complemented with
tdd.
The way
before.
Are there maybe better tools for our case?
Patrick
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from
Bruce Richardson wrote:
On Tue, Mar 17, 2009 at 09:15:59AM +0100, Patrick Debois wrote:
Sorry if this might be slightly off topic here. But it might be you have
encountered a similar problem.
The only sure way to control what is pushed/pulled to your systems is to
maintain a local
Bruce Richardson wrote:
On Tue, Mar 17, 2009 at 10:48:23AM +0100, Patrick Debois wrote:
The only sure way to control what is pushed/pulled to your systems is to
maintain a local package mirror. Then you can make sure that only
the packages you want are visible to your hosts
Lets say that one defines a group resource sans the ensure=present
statement, and also neglects to put any require=Group[foo] statements
into any other resources. Will this resource have any effect?
-Patrick
P.S.
I realize now after typing up the question that the issue probably
applies
601 - 605 of 605 matches
Mail list logo
