inspec/test/fixtures/profiles/waivers
Nick Schwaderer a1129f9efc Allows input and control to have the same name
In https://github.com/inspec/inspec/issues/4936 the issue was reported that naming an input the same as a control caused an unexpected failure.

In that particular case, the naming was a result of a pre-waivers workaround which is no longer necessary, but ultimately a breakage of that name clash is an unexpected occurrance.

Due to how inputs are named and registered, `__apply_waivers` thinks that an object is a waiver that is not a waiver and tries to process it. On the micro level, it breaks when trying to pass a variable to a string as if it were a Hash.

It is imperative that we preserve 100% of the current featureset, pass our tests, and fix this edge case along with new test coverage for the failure.

This PR updates the code to do a slightly more elegant and small ‘waiver check’ to stop the namespace clash from breaking our code.

Signed-off-by: Nick Schwaderer <nschwaderer@chef.io>
2020-05-05 10:00:19 +01:00
..
basic Moved test/unit/mock/* to test/fixtures 2019-11-08 16:29:03 -08:00
namespace-clash Allows input and control to have the same name 2020-05-05 10:00:19 +01:00
only_if Moved test/unit/mock/* to test/fixtures 2019-11-08 16:29:03 -08:00
small Moved test/unit/mock/* to test/fixtures 2019-11-08 16:29:03 -08:00
waiver-child Moved test/unit/mock/* to test/fixtures 2019-11-08 16:29:03 -08:00
waiver-wrapper Moved test/unit/mock/* to test/fixtures 2019-11-08 16:29:03 -08:00