-
Here are my results from running `mix test` in a newly created `mix new` application that depends on Amrita 0.1.3: https://gist.github.com/reinh/88216faeebe85c042328.
I am getting an Elixir stack tra…
reinh updated
11 years ago
-
Every matcher should have a failure case:
Much like suggested here:
https://github.com/josephwilk/amrita/commit/ecd0111e019d589b504d4c41958c4f7f8eb2eeaa
-
-
Currently mocks don't support arguments. Add simplest example:
Exact matches on arguments.
``` elixir
defmodule Polite do
def swear?(words) do
false
end
end
fact do
provided [Polite.swear…
-
Currently
``` elixir
[1,2,3,4,5] |> has_prefix [1,3, 2] # Fails
```
Using Erlang sets we could indicate order does not matter:
``` elixir
[1,2,3,4,5] |> has_prefix :sets.from_list [1,3,2] # Pass
`…
-
``` elixir
defmodule X do
def bing do
false
end
end
fact "stub" do
given X.bing |> true do
X.bing |> truthy
end
end
```
-
The message is ugly, migrate to our own version of assert floats (roughly).
-
Currently fails:
``` elixir
fact "mock with an argument" do
provided [MocksTest.Funk.hip?(:yes, :no) |> false] do
Funk.hip?(:yes, :no) |> falsey
end
end
```
Because the fn here onl…
-
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.
``` elixir
fact "mock with an el…
-
Improve the provided syntax. Feels a little odd having two blocks.
``` elixir
fact "this is a mock" do
provided [Monkey.banana |> :yum] do
Monkey.banana |> :yum
end
end
```
Suggestion:
``` …