summaryrefslogtreecommitdiff
path: root/spec/functions/load_module_metadata_spec.rb
AgeCommit message (Collapse)Author
2017-03-03(FM-6063) - Unit tests for high effort functionsPaula McMaw
2017-02-04Allow test module metadata.json to be readDominic Cleal
Since puppetlabs/puppet@f2e8e66, the test module's metadata.json is also read causing expectation failures. Like 5c51463, permit it to be read by Puppet.
2017-01-24(MODULES-4098) Sync the rest of the filesHunter Haugen
2016-07-01Fix load_module_metadata and loadjson tests to pass with fully deployed moduleDavid Schmitt
When replacing the lib/ and manifests/ symlinks in the fixtures with a proper top-level symlink, puppet 4 starts loading the metadata.json before loading functions, which confuses these tests. Added more specific expectations, and provide data for that call.
2015-10-14Let load_module_metadata succeed on empty fileColleen Murphy
Some modules or module versions don't have a metadata.json file, but we might still want to use the load_module_metadata function on them. The lack of a file can still give us important information. For example, it might tell us that the version of the module installed is "very old" even if we can't read the version number directly. This patch adds a parameter to let the user specify if an empty file is acceptable. To preserve backwards compatibility it does not change the current default behavior, which is to raise an error if metadata.json does not exist.
2015-10-14Rename load_module_metadata test pathColleen Murphy
`rake spec` only finds test files that end in _spec.rb, so this test was not being run. Correct the path name so that the test runs properly.