Packages

phx_new

1.3.5
1.8.9 1.8.8 1.8.7 1.8.6 1.8.5 1.8.4 1.8.3 1.8.2 1.8.1 1.8.0 1.8.0-rc.4 1.8.0-rc.3 1.8.0-rc.2 1.8.0-rc.1 1.8.0-rc.0 1.7.24 1.7.23 1.7.22 1.7.21 1.7.20 1.7.19 1.7.18 1.7.17 1.7.16 1.7.15 1.7.14 1.7.13 1.7.12 1.7.11 1.7.10 1.7.9 1.7.8 1.7.7 1.7.6 1.7.5 1.7.4 1.7.3 1.7.2 1.7.1 1.7.0 1.7.0-rc.3 1.7.0-rc.2 1.7.0-rc.1 1.7.0-rc.0 1.6.17 1.6.16 1.6.15 1.6.14 1.6.13 1.6.12 1.6.11 1.6.10 1.6.9 1.6.8 1.6.7 1.6.6 1.6.5 1.6.4 1.6.3 1.6.2 1.6.1 1.6.0 1.6.0-rc.1 1.6.0-rc.0 1.5.15 1.5.14 1.5.13 1.5.12 1.5.11 1.5.10 1.5.9 1.5.8 1.5.7 1.5.6 1.5.5 1.5.4 1.5.3 1.5.2 1.5.1 1.5.0 1.5.0-rc.0 1.4.18 1.4.17 1.4.16 1.4.15 1.4.14 1.4.13 1.4.12 1.4.11 1.4.10 1.4.9 1.4.8 1.4.7 1.4.6 1.4.5 1.4.4 1.4.3 1.4.2 1.4.1 1.4.0 1.4.0-rc.3 1.4.0-rc.2 1.4.0-rc.1 1.4.0-rc.0 1.4.0-dev.0 1.3.5

Phoenix framework project generator. Provides a `mix phx.new` task to bootstrap a new Elixir application with Phoenix dependencies.

HexDocs

Current section

Files

Jump to
Readme
106 Versions
0 Dependencies
5 Dependants
Files
Activity
phx_new templates ecto model_case.ex
Raw

templates/ecto/model_case.ex 

defmodule <%= app_module %>.ModelCase do

  @moduledoc """

  This module defines the test case to be used by

  model tests.



  You may define functions here to be used as helpers in

  your model tests. See `errors_on/2`'s definition as reference.



  Finally, if the test case interacts with the database,

  it cannot be async. For this reason, every test runs

  inside a transaction which is reset at the beginning

  of the test unless the test case is marked as async.

  """



  use ExUnit.CaseTemplate



  using do

    quote do

      alias <%= app_module %>.Repo



      import Ecto

      import Ecto.Changeset

      import Ecto.Query

      import <%= app_module %>.ModelCase

    end

  end



  setup tags do

    <%= adapter_config[:test_setup] %>



    unless tags[:async] do

      <%= adapter_config[:test_async] %>

    end



    :ok

  end



  @doc """

  Helper for returning list of errors in a struct when given certain data.



  ## Examples



  Given a User schema that lists `:name` as a required field and validates

  `:password` to be safe, it would return:



      iex> errors_on(%User{}, %{password: "password"})

      [password: "is unsafe", name: "is blank"]



  You could then write your assertion like:



      assert {:password, "is unsafe"} in errors_on(%User{}, %{password: "password"})

  """

  def errors_on(struct, data) do

    struct.__struct__.changeset(struct, data)

    |> Ecto.Changeset.traverse_errors(&<%= app_module %>.ErrorHelpers.translate_error/1)

    |> Enum.flat_map(fn {key, errors} -> for msg <- errors, do: {key, msg} end)

  end

end