How to test a Phoenix Controller with Hammox?

I am not very familiar with them, but looking at the Mox library and hammox, I don’t think StorageMock is coming from the library. I cannot find any reference to it in the hammox or mox hexdocs.

According to the Mox documentation, you have to define your own custom behavior. My understanding is that you define a real behavior and a mock behavior and then switch to the mock during tests. A good example is in the readme for mox.

https://github.com/dashbitco/mox?tab=readme-ov-file#4-define-the-mock-so-it-is-used-during-tests

StorageMock is my equivalent of DatabaseMock from this README (GitHub - msz/hammox: 🏝 automated contract testing via type checking for Elixir functions and mocks · GitHub).

The behaviour is called Storage, and StorageMock is the Mock for said behaviour.

Both Hammox and Mox work the same way in this regard.

Based on the error message, it seems like the application is referencing StorageMock during boot and crashing.

That module isn’t defined until something says Hammox.defmock(StorageMock, for: MyApp.Storage) - you may need to put that call in your test_helper.exs to get it to happen before application boot.

test_helper.exs is also loaded after application startup. What works is putting the defmock in a compiled file (not a script), e.g. in test/support/mocks.ex or something like that. See the documentation here: Mox — Mox v1.1.0

This is really close to the problem. Turns out my issue was that I was referencing StorageMock at application startup, namely:

defmodule MyApp.Application do
  @moduledoc false

  use Application

  @impl true
  def start(_type, _args) do
   children = 
    [
      MyAppWeb.Telemetry,
      {Phoenix.PubSub, name: MyApp.PubSub},
      {StorageMock, []},
      MyAppWeb.Endpoint
    ]

    opts = [strategy: :one_for_one, name: MyApp.Supervisor]
    Supervisor.start_link(children, opts)
  end
end

By removing StorageMock from the list of children (when running tests) the error was fixed.

For those of you curious, you can check in which env the application is running, by using Mix.env(). Thus, you can do something like:

  def start(_type, _args) do
    opts = [strategy: :one_for_one, name: MyApp.Supervisor]
    Supervisor.start_link(children(Mix.env(), opts)
  end

  defp children(:test) do
    [
      MyAppWeb.Telemetry,
      {Phoenix.PubSub, name: MyApp.PubSub},
      MyAppWeb.Endpoint
    ]
  end

  defp children(_other_envs) do
    [
      MyAppWeb.Telemetry,
      {Phoenix.PubSub, name: MyApp.PubSub},
      {RealStorage, ["localhost:5221"]},
      MyAppWeb.Endpoint
    ]
  end

This is the solution I ended up going with, as it means you can make use of the config/test.exs to define what modules you want to use. You can even change modules at runtime by using Application.put_env/3 if you are inclined to do that, which can also come in handy when doing some specific types of tests.

Thanks for the help!