inspec/test
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
..
artifact Fix artifact-habitat testing for inspec. 2020-02-10 18:34:00 -08:00
fixtures Allows input and control to have the same name 2020-05-05 10:00:19 +01:00
functional Allows input and control to have the same name 2020-05-05 10:00:19 +01:00
helpers Merge pull request #4822 from PiQuer/master 2020-01-31 16:41:27 -08:00
integration move find_files inspec policy to kitchen directory 2019-10-16 22:41:03 -07:00
kitchen replaced instances of have_protocols with have_protocol in documentation and examples 2019-12-31 10:51:55 -05:00
unit Merge pull request #4954 from tecracer-theinen/feature/virtualization-detection 2020-04-06 10:23:58 +01:00
helper.rb Push Windows test skipping for 2 more months 2020-05-04 14:55:51 +01:00