inspec/test/unit/profiles/library_eval_context_tests.rb
Steven Danna 9bb65bd60c Use per-profile execution contexts for library loading
Previously, libraries were loaded by instance_eval'ing them against
the same execution context used for control files.  All resources were
registered against a single global registry when the `name` dsl method
was invoked.  To obtain seperation of resources, we would mutate the
instance variable holding the globale registry and then change it back
at the end.

Now, we instance_eval library files inside an anonymous class.  This
class has its own version of `Inspec.resource` that returns another
class with the resource DSL method and the profile-specific resource
registry.
2016-09-04 20:55:20 +02:00

40 lines
996 B
Ruby

# encoding: utf-8
# author: Steven Danna
require 'helper'
require 'inspec/resource'
require 'inspec/library_eval_context'
describe Inspec::LibraryEvalContext do
let(:resource_content) { <<EOF
class MyTestResource < Inspec.resource(1)
name 'my_test_resource'
desc 'A test description'
example 'Forgot to write docs, sorry'
def version
'2.0'
end
end
EOF
}
let(:registry) { Inspec::Resource.new_registry }
let(:eval_context) { Inspec::LibraryEvalContext.create(registry, nil) }
it 'accepts a registry' do
Inspec::LibraryEvalContext.create(registry, nil)
end
it 'adds the resource to our registry' do
eval_context.instance_eval(resource_content)
registry.keys.include?("my_test_resource").must_equal true
end
it 'adds nothing to the default registry' do
old_default_registry = Inspec::Resource.default_registry.dup
eval_context.instance_eval(resource_content)
old_default_registry.must_equal Inspec::Resource.default_registry
end
end