creating mocks in test setup causes mock module name conflict warnings

[wanderanimrod]

creating mocks in test setup causes mock module name conflict warnings

[wanderanimrod]

Lines of thought

• Macros are evaluated once at compile time.
• Cached evaluations of the macros are injected whenever a macro is called with the same arguments many times??? (seems like it)
• ExUnit's setup macro injects the setup code into each test??

Workaround:

Use Code.compiler_options(ignore_module_conflict: true) when defining mocks in test setup functions

setup do
  Code.compiler_options(ignore_module_conflict: true)
  with_mock(my_mock) = defmock_of RealModule do
    def stub(), do: :stubbed
  end
  Code.compiler_options(ignore_module_conflict: false)
end

Remember to apply Code.compiler_options(ignore_module_conflict: false) after the mock definition.

[wanderanimrod]

Closing this for now. Let me know if the workaround doesn't suffice in your case and I'll reopen this investigation.