Closed rnelson0 closed 8 years ago
This is an issue with gem 2.4.0 now that it is released. I can either disable strict variables or pin to 2.3.2.
This is still occurring. See https://gist.github.com/rnelson0/8ce6aae9ba105b0729efc739dc8c34e6 for detailed reproduction steps.
@rnelson0 the test uses a fact that is not supplied in the facts of the agent_spec. This causes expected test failures under STRICT_VARIABLES. If tests passed before, assume that earlier rspec-puppet versions didn't setup the puppet configuration properly under STRICT_VARIABLES.
@DavidS Ooof. That makes sense but that hurts.
Yeah, quite a bummer that one. :-(
I'm still not sure how glad I am that we found it. But in the end, I think, honest tests win over short-term pain. Adding a few facts to test suites usually is not that much effort.
In rspec-puppet 2.3.2, or from git up to commit 6bbedd2, rspec with strict variables seems to work fine. However, moving past that to commit 5a54c7e results in new errors showing up.
As I can resolve this immediately by changing my Gemfile to use the older commit or to pull from rubygems, I believe this is a regression in commit 5a54c7e.