Register Test or Mock Provider

[toddkummer]

I find myself using dependency injection to mock the Chat in my tests. Could we have a mock or test provider that you could register before running tests that would simply handle the calls to it and allow for some inspection.

Here's what a quick-and-dirty chat mock looks like, just to start the discussion:

class ChatMock < RubyLLM::Chat
  attr_reader :questions, :instructions

  def initialize
    @messages = []
  end

  def with_instructions(instructions)
    (@instructions ||= []) << instructions
    self
  end

  def ask(question)
    (@questions ||= []) << question
     add_message role: :user, content: RubyLLM::Content.new("This could be injected in the test")
    end
  end
end

I think it would be cleaner to do this at the provider level rather than mocking each chat.

[crmne]

Testing is application responsibility, not library responsibility. Your dependency injection approach is exactly the right solution - clean, flexible, and doesn't add complexity to the library.

RubyLLM focuses on LLM communication. Adding test providers would bloat the library with auxiliary concerns that every application handles differently.

Keep using your current approach.