I have an open bug report with the rspec-puppet project (https://github.com/rodjek/rspec-puppet/issues/316) whereby the coverage from testing custom functions in my modules are not cumulative but only include coverage from the last expectation which results in reports showing low percentages.
Anyway, I've now noticed that if I use Puppet 4.x (4.4.2 in this case) to run the test suite then I get zero code coverage which I've tracked down to the fact that the custom functions are shown in the report to be located in `spec/fixtures/modules/<my module>/lib/puppet/parser/functions/...` and the whole of `spec/` is normally filtered out of the coverage report to prevent the tests themselves and any Ruby code in dependent modules from contributing. If I go back to Puppet 3.x (3.8.7) then the custom functions are shown to be located in `lib/puppet/parser/functions/...` again as expected. I have a small test module that I used to demonstrate the original bug available here: https://github.com/bodgit/puppet-test Is this change in behaviour expected? Matt -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20160513134022.GC13102%40simulant.bodgit-n-scarper.com. For more options, visit https://groups.google.com/d/optout.
