[no description] https://git.osdyson.ru/pkg-puppet/puppet/atom?h=master 2014-05-13T00:28:38Z 2014-05-13T00:28:38Z Josh Partlow joshua.partlow@puppetlabs.com 2014-05-12T23:53:30Z urn:sha1:97d722381ec4a62ae8dcdff536cd014092b99957 Fixes some rdoc1 spec issues by providing explicit envs in the specs. 2014-04-28T21:04:58Z Josh Partlow joshua.partlow@puppetlabs.com 2014-04-23T01:27:48Z urn:sha1:779f012ad6dfca2de252cf2edc50668c7409e67b A few specs relying on mocking Puppet::Node::Environment.new to return a specific test environment were colliding with the new environments cacheing layer. Switched to using puppet override to supply a static environment. 2014-04-07T15:01:38Z Andrew Parker andy@puppetlabs.com 2014-04-07T15:01:38Z urn:sha1:f6637b0a3dba8bed9cd039ff22e644ea38040a84 The tests were often creating environments that didn't need to have manifests. Since we didn't have a way of specifying that when they were written, we used '' to fill in the blank. This actually caused a large number of tests to try to find code to load in the PWD, which caused tests to break if a developer had parse errors in manifests being used for testing in the root directory of their puppet project. This changes the manifest to be optional and removes '' from those tests. The tests no longer fail if a bad manifest is in the PWD :D 2014-01-29T18:52:10Z Josh Partlow joshua.partlow@puppetlabs.com 2014-01-29T18:52:10Z urn:sha1:f381f2c758c770e6e3e8ec4e3cb2b6ed3670f423 PuppetParserCore was updated to pass environment, known_resource_types; this just catches up the spec, which runs only on 1.8.7, to match the changes. 2014-01-06T18:06:06Z Henrik Lindberg henrik.lindberg@cloudsmith.com 2014-01-05T21:41:14Z urn:sha1:e15cae88317b770a95afd626e01e666106ff35ee 2013-12-20T14:30:57Z Ethan J. Brown Iristyle@github 2013-12-19T18:03:08Z urn:sha1:ba09bfe99d9ac8679b74259e55c7b31947d05d1b - Previously tests were writing to the shared %ALLUSERSPROFILE%\PuppetLabs\puppet directory, and would blow up if this directory did not exist - Because this directory was shared from one run to the next, failing tests could be masked by data generated / used by a locally installed Puppet - The stubbing of FileSystem::File.exist? to return true was causing some tests to treat files like c:\dev\null\foo to attempt to be loaded, which would cause these tests to fail in isolation, but not when run within the suite - Had to change some doc specs under Ruby 1.9 / OSX to verify a value instead of asserting a method was called, to prevent a stack overflow - In some unit tests, the process of reading / writing settings caused issues with test loading, so Puppet.settings.use has been stubbed 2013-11-08T23:51:39Z Ethan J. Brown Iristyle@github 2013-10-31T13:38:26Z urn:sha1:4bd6f875a02ddfbf50c1b20aea9d7ab46a76695b - All calls to File class stat / lstat go through the new FileSystem::File abstraction so that the implementation can later be swapped for a Windows specific one to support symlinks 2013-10-25T21:21:23Z Josh Partlow joshua.partlow@puppetlabs.com 2013-10-25T21:21:23Z urn:sha1:cedd593ddcdac7735ae4af9ac6e022ce4d388a28 RDoc 2+ has an RDoc::ClassModule.add_comment(comment,location) method which is the preferred method of setting comments for a class. RDoc shipping with Ruby 1.9 seems to fall back to using the @comment, which is how rdoc1 handled this, but Ruby 2.0's rdoc seems to be stricter and requires use of add_comment. This patch overrides the add_comment method in our PuppetModule, PuppetClass, PuppetNode code objects with a version compatible with either rdoc1 or 2. It also tests for module level README comments being incorporated. 2013-10-25T00:18:44Z Josh Partlow joshua.partlow@puppetlabs.com 2013-10-25T00:18:44Z urn:sha1:7f59b3a383dbc97eb81101b91b77e5c9a1f9675c There were a number of rdoc1 features (tracking of included, required modules, realized virtual resources, all resources when :document_all setting is true, and global variables) which had not been functioning due to the parser wrapping statements in Puppet::Parser::AST::BlockExpression instances now rather than Puppet::Parser::AST::Array instances. This is now fixed so that these areas are documented when using rdoc1. Only included classes is documented in rdoc2, however. Documenting the remaining elements would require writing a new renderer. 2013-05-29T18:17:18Z Josh Cooper josh@puppetlabs.com 2013-05-29T03:44:41Z urn:sha1:650392545c6c3a3c963076343b27690aea9e426a Nested rspec include filters don't work the way I expect. Given: describe "A", :if => rdoc1? do before :all do require 'rdoc/tokenstream' end describe "B", :if => windows? do end end If rdoc1? is false, but windows? is true, the before :all/:each blocks will still be executed, and the tests in B will be executed. As a result, the spec tests fail on Windows and ruby 1.9, because our rdoc parser is not compatible with newer versions of rdoc. For example, rdoc/tokenstream.rb was moved to token_stream.rb, etc. This commit adds the rdoc1? predicate to the example group B, so that it is not executed when rdoc1? is false.