-1

我的第二次测试失败了。

 1) test it jumps when it can (RunnerTest)
     test/runner_test.exs:15
     No message matching %{y: 1} after 100ms.
     The process mailbox is empty.
     stacktrace:
       test/runner_test.exs:18: (test)

defmodule RunnerTest do
  use ExUnit.Case
  doctest Runner

  setup_all do
    {:ok, pid: spawn(fn -> Runner.input() end)}
  end

  test "it increases its x position", state do
    avatar = %{x: 0, y: 0}
    send state[:pid], {:run, self, avatar}
    assert_receive %{x: 1}
  end

  test "it jumps when it can", state do
    avatar = %{x: 0, y: 0}
    send state[:pid], {:jump, self, avatar}
    assert_receive %{y: 1}
  end

end

流道模块:

defmodule Runner do
    def input do
      receive do
       {:run, sender, mover} -> send sender, run(mover)
       {:jump, sender, mover} -> send sender, jump(mover)
     end
    end

    defp run(mover) do
        Map.merge(mover, %{x: mover.x + 1})
    end

    defp jump(mover) do
        case {mover.y} do
          {0} ->
            Map.merge(mover, %{y: mover.y + 1})
          _ ->
            mover
        end
    end

end

该测试通过:

 test "it jumps when it can", state do
    avatar = %{x: 0, y: 0}
    pid = spawn(fn -> Runner.input() end)
    send pid, {:jump, self, avatar}
    assert_receive %{y: 1}
  end

为什么 1 个测试(运行)与 setup 一起工作,而不是另一个(jump)?

4

1 回答 1

1

为什么 1 个测试(运行)与 setup 一起工作,而不是另一个(jump)?

这是因为您的进程只响应一条消息然后死亡并且您正在使用setup_all而不是setup,这意味着该进程仅在运行第一个测试之前启动一次,并且相同pid的内容传递给所有测试。

您可以更改setup_allsetup是否要为每个测试生成一个新进程,或者让您的进程响应多于 1 条消息(使用自递归可能是无限的)。

于 2016-10-18T15:52:44.460 回答