Hi There,
I am kind of lost, understood something wrong. I have written a module.
Now how can I test this module? Do I need to copy it to agent or server? Is
it possible to test it as a standalone module where I have a machine with
puppet agent or server installed? It is a simple module I
Hi Raj,
when running puppet apply on your module init.pp you will only compile the
module but you will not instantiate the module.
(google for definition vs. declaration)
You need to create another init.pp file (normally you put them into
yourmodule/tests/init.pp).
In this file you declare the
Hi Raj,
when running puppet apply on your module init.pp you will only compile the
module but you will not instantiate the module.
(google for definition vs. declaration)
You need to create another init.pp file (normally you put them into
yourmodule/tests/init.pp).
In this file you declare the
I'm in the process of trying to get automated testing for my modules, using
puppet-lint, rspec-puppet, puppetlabs_spec_helper and Jenkins.
Are there any automated, or semi-automated ways to ensure coverage on my
tests? At the moment I am writing tests for existing modules, but I also
need to
Hi,
It sounds like you would like to reduce some of the boilerplate code around
your testing? I happened to notice this article you may find useful:
http://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing/
best wishes, JS
--
You received this message because you are
Hullo
I'm trying to work out the best way to use Puppet to control an
existing estate, and then how to refactor the configurations. I'd like
to use the appropriate tools where I can (eg taking distros to get
consistent sets of packages, package managers for the bulk of
deployment). During the
* Tim Coote [2011-06-01]:
I'm trying to work out the best way to use Puppet to control an
existing estate, and then how to refactor the configurations. I'd like
I don't believe there to be a best way, it depends on your situation.
When I introduced puppet at our company, I chose to start from
