fe5616cfca
The previous use of require caused File.join on several occasions to calculate different paths to the same library, depending on which __FILE__ the library was being calculated as relative to; e.g. /some/path/prefix/spec/one/bar.rb would do the equivalent of: require '/some/path/prefix/spec/one/../../libraries/foo/mylib.rb' and /some/path/prefix/spec/two/baz.rb would do the equivalent of: require '/some/path/prefix/spec/two/../../libraries/foo/mylib.rb' This would result in mylib.rb being loaded multiple times, causing warnings from constants being redefined, and worse, multiple objects representing the same class hierarchy (@@foo) variables. The latter actually broke the @@subclasses registration mechanism in Pacemaker::CIBObject. By switching to File.expand_path, we ensure we always refer to each library using a single absolute path, which means Ruby's require mechanism works as it should, only loading the code the first time round.
28 lines
750 B
Ruby
28 lines
750 B
Ruby
require 'spec_helper'
|
|
require File.expand_path('../../../../libraries/pacemaker/constraint/colocation',
|
|
File.dirname(__FILE__))
|
|
require File.expand_path('../../../fixtures/colocation_constraint', File.dirname(__FILE__))
|
|
require File.expand_path('../../../helpers/common_object_examples', File.dirname(__FILE__))
|
|
|
|
describe Pacemaker::Constraint::Colocation do
|
|
let(:fixture) { Chef::RSpec::Pacemaker::Config::COLOCATION_CONSTRAINT.dup }
|
|
|
|
before(:each) do
|
|
Mixlib::ShellOut.any_instance.stub(:run_command)
|
|
end
|
|
|
|
def object_type
|
|
'colocation'
|
|
end
|
|
|
|
def pacemaker_object_class
|
|
Pacemaker::Constraint::Colocation
|
|
end
|
|
|
|
def fields
|
|
%w(name score resources)
|
|
end
|
|
|
|
it_should_behave_like "a CIB object"
|
|
end
|