similar to: Announce: puppetlabs_spec_helper 0.1.0 Available

Hi, I was playing with rspec and every time I find a possible improvement that could be made in spec_helper or rakefile I have to change it in every module that is using rspec tests. So maybe these things could be centralized, I thought to myself. I found the following module, actually. https://github.com/puppetlabs/puppetlabs-module_spec_helper But I am at a lost how to use it. Is it supposed

I am using puppet 2.7.14 on Ubuntu 10.04 LTS. I have the following gems: *** LOCAL GEMS *** diff-lcs (1.1.3) hiera (0.3.0) hiera-puppet (0.3.0) metaclass (0.0.1) mocha (0.12.1) puppet-lint (0.1.13) puppetlabs_spec_helper (0.2.0) rake (0.9.2.2) rspec (2.11.0) rspec-core (2.11.1) rspec-expectations (2.11.2) rspec-mocks (2.11.1) rspec-puppet (0.1.3) When I run "rake help" I get the

I''m trying to get rspec-puppet working and have run into a problem. I have a VM running ubuntu lucid, have installed rubygems 1.3.5 from the apt package and have install rspec-puppet (and other required gems), and rake, using gem install. I''ve run rspec-puppet-init in the module I want to test, and have created a very basic spec file for one of the classes in my module.

I''m trying to make puppetlabs_spec_helper runs on Windows 7 to test my Puppet modules. Is this supported ? Because I encountered some problems: 1. symlinks were not created on Windows 7 (even if the functionnality are availabe). To manage that I added to rake_tasks.rb an ugly function: def make_link(source,target) ruby_platform =

Hello, I''m writing my first puppet function rspec test and am having a problem which I don''t see how to solve. The function (and the test) involve access to files through the File Server. In order for the function (and the test) to work I need to pass "--fileserverconf=fileserver.conf" parameter to Puppet. So far I haven''t found a way to do that. If I

puppetlabs_spec_helper is a Rubygem to make writing and running module spec tests using rspec-puppet easier. It includes a set of common rake tasks and a spec_helper that correctly initializes puppet and rspec-puppet for testing. Changes: * Rake should fail if git can''t clone repository * add backwards-compatible support for arbitrary git refs in .fixtures.yml * Only remove the

I''ve been working on getting spec tests on all of my modules and am down to ones that use hiera and don''t have any reasonable defaults. It looks like there is a project on GH (https://github.com/amfranz/rspec-hiera-puppet) that is designed to fill this need, but for the life of me I cannot make it work. FriedBob helped out on the IRC channel some with his solution of including

Hey Gang, Running into a weird error when trying to follow puppetlabs'' blog: https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing/ I''m running 10.8.2, using default ruby, in an attempt to make my home env a little more sane, (ran into weird rbenv issues at work, which I won''t go into here) The google tells me not a whole lot. Appreciate any help

Hello all, I have created this module: https://github.com/Spantree/puppet-thrift and everything worked fine all specs ran fine. Now I using the puppetlabs/apt module and when I run the 'rake spec' it is trying to run the 'apt' tests, and it is failing (I think) because I am not providing the appropriate facts. Is there a way to ignore the rspecs inside the

Does puppet doc require a specific version of any gems (such as rdoc or rake) to operate? I''m getting some errors when I try to generate my rdoc now. # puppet doc --output /var/www/test --modulepath /etc/puppet/environments/test/modules -m rdoc RDoc::RDocError is deprecated and will be removed in RDoc 4 Could not generate documentation: uninitialized constant RDoc::RDoc::Generator

Hello, We''re pleased to announce the release of the stdlib module at version 3.0.0 [1]. This major release drops compatibility with Puppet 2.6 and preserves compatibility with Puppet 2.7. The 2.x series will persist for compatibility and bugfix releases for Puppet 2.6. New features intended to work with Puppet 2.6 may be included into a future stdlib 2.5 release, as there are still

Hi all, There is something amiss with what I am doing. I believe the following should work. puppetlabs_spec_helper (0.3.0) rspec (2.11.0) rspec-core (2.11.1) rspec-expectations (2.11.2) rspec-mocks (2.11.1) rspec-puppet (0.1.4) . ├── manifests │   └── init.pp ├── Rakefile └── spec ├── classes │   └── testthis_spec.rb ├── defines ├── fixtures │   ├── manifests │   │   └──

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 be able to be relatively certain that tests are updated as modules are, and minimize reliance

Hi, I just updated to the latest RSpec 1.1.3 + ZenTest 3.9.1. I also have rspec 1.1.3 installed as a gem When starting autotest with -v option, there is a lot of noise because autotest does not ignore the vendor folder, the migrations, etc ...: Dunno! vendor/plugins/acts_as_solr/solr/lib/jetty-util-6.1.3.jar Dunno!

We have an odd situation with a puppet 3 installation. It isnt serving out the module local files. We understand (Somewhat) about the new auth.conf requirements, and have filled those out. So, access to things such as puppet:///files/etc/somefile.conf are working fine. However, attempts to access puppet:///modulename/somefile.conf fail, with (in the case of modulename==java) Error:

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

On UNIX, I am executing an rsync command, from within a script. The command goes something like this: /usr/bin/rsync --verbose --progress --stats --compress --recursive --times --perms --links --safe-links source_dir/ user at target_machine:/parent_path/source_dir In other words, I am replicating source_dir on a remote machine. It ends up next to a lot of sibling, directories, like this: On

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that

I''ve been looking at bottling some functionality up into a plugin, but I''m having some problems including it. The structure I have is: /app/controllers/admin/base_controller.rb: class Admin::BaseController > ApplicationController #snip# end /vendor/plugins/myplugin/lib/my_module.rb: module MyModule def new_func "New Function" end end