Currently since meck is being used for mocking it messes up anything that expands into a tuple in Elixir (such as a regex). Since Erlang does not know what that is.
fact "mock with an elixir argument" do
provided [MocksTest.Funk.hip?(%r"monkey") |> false] do
Funk.hip?(%r"monkey") |> falsey
end
end
And the result:
"MocksTest.Funk.hip?({%r\"monkey\",[]}) called 0 times." |> called("Expected atleast once")
Suspect this is leading towards doing the argument matching ourselves from the history rather than let meck handle it.
Currently since meck is being used for mocking it messes up anything that expands into a tuple in Elixir (such as a regex). Since Erlang does not know what that is.
And the result:
Suspect this is leading towards doing the argument matching ourselves from the history rather than let meck handle it.
Types: