|
8 | 8 |
|
9 | 9 | * [Installation](#installation)
|
10 | 10 | * [Starting out with a new module](#starting-out-with-a-new-module)
|
11 |
| -* [Configure manifests for Puppet 4](#configure-manifests-for-puppet-4) |
12 | 11 | * [Configuration](#configuration)
|
13 | 12 | * [Naming conventions](#naming-conventions)
|
14 | 13 | * [Example groups](#example-groups)
|
@@ -997,23 +996,26 @@ end
|
997 | 996 | ```
|
998 | 997 |
|
999 | 998 | Resources declared outside of the module being tested (i.e. forge dependencies)
|
1000 |
| -are automatically removed from the coverage report. There is one exception for |
1001 |
| -this though: **prior to Puppet 4.6.0**, resources created by functions |
1002 |
| -(create\_resources(), ensure\_package(), etc) did not have the required |
1003 |
| -information in them to determine which manifest they came from and so can not |
1004 |
| -be excluded from the coverage report. |
| 999 | +are automatically removed from the coverage report. |
1005 | 1000 |
|
1006 | 1001 | ## Related projects
|
1007 | 1002 |
|
1008 | 1003 | * [puppetlabs_spec_helper](https://github.com/puppetlabs/puppetlabs_spec_helper): shared spec helpers to setup puppet
|
1009 |
| -* [rspec-puppet-augeas](https://github.com/domcleal/rspec-puppet-augeas): RSpec tests for Augeas resources inside Puppet manifests |
1010 |
| -* [jimdo-rspec-puppet-helpers](https://github.com/Jimdo/jimdo-rspec-puppet-helpers): Tests the contents of a file with a source |
1011 |
| -* Ease development of specs |
1012 |
| - * [puppet-catalog_rspec](https://github.com/enterprisemodules/puppet-catalog_rspec): Dump the Puppet Catalog as RSpec code at compile time |
1013 |
| - * [create_specs](https://github.com/alexharv074/create_specs.git): A different implementation that takes a compiled catalog and writes out RSpec code with various options |
1014 | 1004 | * Fact providers
|
1015 |
| - * [rspec-puppet-facts](https://github.com/mcanevet/rspec-puppet-facts): Simplify your unit tests by looping on every supported Operating System and populating facts. |
1016 |
| - * [rspec-puppet-osmash](https://github.com/Aethylred/rspec-puppet-osmash): Provides Operation System hashes and validations for rspec-puppet |
1017 |
| - * [puppet_spec_facts](https://github.com/danieldreier/puppet_spec_facts): Gem to provide puppet fact hashes for rspec-puppet testing |
| 1005 | + * [rspec-puppet-facts](https://github.com/voxpupuli/rspec-puppet-facts): Simplify your unit tests by looping on every supported Operating System and populating facts. |
1018 | 1006 |
|
1019 | 1007 | For a list of other module development tools see [DevX Tools](https://puppetlabs.github.io/content-and-tooling-team/tools/), or from our trusted Voxpupuli community [here](https://voxpupuli.org/plugins/).
|
| 1008 | + |
| 1009 | +## Reporting bugs or incorrect results |
| 1010 | + |
| 1011 | +If you find a bug in Puppet Lint or its results, please create an issue in the repo issues tracker. Bonus points will be awarded if you also include a patch that fixes the issue. |
| 1012 | + |
| 1013 | +## Development |
| 1014 | + |
| 1015 | +If you run into an issue with this tool or would like to request a feature you can raise a PR with your suggested changes. Alternatively, you can raise a Github issue with a feature request or to report any bugs. Every other Tuesday the DevX team holds office hours in the Puppet Community Slack, where you can ask questions about this and any other supported tools. This session runs at 15:00 (GMT/BST) for about an hour. |
| 1016 | + |
| 1017 | +If you have problems getting this tool up and running, please contact Support. |
| 1018 | + |
| 1019 | +## Thank you |
| 1020 | + |
| 1021 | +Many thanks to the original author of rspec-puppet Tim Sharpe (@rodjek). |
0 commit comments