lecture 06

lectures/06/counter/test/counter_web/controllers/error_json_test.exs

@@ -0,0 +1,12 @@
+defmodule CounterWeb.ErrorJSONTest do
+  use CounterWeb.ConnCase, async: true
+
+  test "renders 404" do
+    assert CounterWeb.ErrorJSON.render("404.json", %{}) == %{errors: %{detail: "Not Found"}}
+  end
+
+  test "renders 500" do
+    assert CounterWeb.ErrorJSON.render("500.json", %{}) ==
+             %{errors: %{detail: "Internal Server Error"}}
+  end
+end

lectures/06/counter/test/support/conn_case.ex

@@ -0,0 +1,37 @@
+defmodule CounterWeb.ConnCase do
+  @moduledoc """
+  This module defines the test case to be used by
+  tests that require setting up a connection.
+
+  Such tests rely on `Phoenix.ConnTest` and also
+  import other functionality to make it easier
+  to build common data structures and query the data layer.
+
+  Finally, if the test case interacts with the database,
+  we enable the SQL sandbox, so changes done to the database
+  are reverted at the end of every test. If you are using
+  PostgreSQL, you can even run database tests asynchronously
+  by setting `use CounterWeb.ConnCase, async: true`, although
+  this option is not recommended for other databases.
+  """
+
+  use ExUnit.CaseTemplate
+
+  using do
+    quote do
+      # The default endpoint for testing
+      @endpoint CounterWeb.Endpoint
+
+      use CounterWeb, :verified_routes
+
+      # Import conveniences for testing with connections
+      import Plug.Conn
+      import Phoenix.ConnTest
+      import CounterWeb.ConnCase
+    end
+  end
+
+  setup _tags do
+    {:ok, conn: Phoenix.ConnTest.build_conn()}
+  end
+end

lectures/06/counter/test/test_helper.exs

@@ -0,0 +1 @@
+ExUnit.start()