Contents

module ShellMock
  StubRegistry = Object.new

  StubRegistry.instance_exec do
    def register_command_stub(command_stub)
      command_stubs << command_stub
      command_stub
    end

    def stub_matching(env, command, options)
      matching_stubs = command_stubs.select do |command_stub|
        command_stub.command == command &&
          command_stub.env <= env &&
          command_stub.options <= options
      end

      # question: Should we increment all the stubs that match?
      #   What should users expect when they register a stub that
      #   wholly "covers" another already-registered stub?
      matching_stubs.max_by do |command_stub|
        [env.size, options.size]
      end
    end

    def command_stubs
      @command_stubs ||= []
    end

    def clear
      @command_stubs = []
    end
  end
end

Version data entries

5 entries across 5 versions & 1 rubygems

Version	Path
shell_mock-0.7.2	lib/shell_mock/stub_registry.rb
shell_mock-0.7.1	lib/shell_mock/stub_registry.rb
shell_mock-0.7.0	lib/shell_mock/stub_registry.rb
shell_mock-0.6.0	lib/shell_mock/stub_registry.rb
shell_mock-0.5.0	lib/shell_mock/stub_registry.rb