adds phoenix boilerplate and database api
- message communication added - database migration added - initial commit
This commit is contained in:
		
							
								
								
									
										36
									
								
								test/support/channel_case.ex
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										36
									
								
								test/support/channel_case.ex
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,36 @@
 | 
			
		||||
defmodule BumpWeb.ChannelCase do
 | 
			
		||||
  @moduledoc """
 | 
			
		||||
  This module defines the test case to be used by
 | 
			
		||||
  channel tests.
 | 
			
		||||
 | 
			
		||||
  Such tests rely on `Phoenix.ChannelTest` 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 BumpWeb.ChannelCase, async: true`, although
 | 
			
		||||
  this option is not recommended for other databases.
 | 
			
		||||
  """
 | 
			
		||||
 | 
			
		||||
  use ExUnit.CaseTemplate
 | 
			
		||||
 | 
			
		||||
  using do
 | 
			
		||||
    quote do
 | 
			
		||||
      # Import conveniences for testing with channels
 | 
			
		||||
      import Phoenix.ChannelTest
 | 
			
		||||
      import BumpWeb.ChannelCase
 | 
			
		||||
 | 
			
		||||
      # The default endpoint for testing
 | 
			
		||||
      @endpoint BumpWeb.Endpoint
 | 
			
		||||
    end
 | 
			
		||||
  end
 | 
			
		||||
 | 
			
		||||
  setup tags do
 | 
			
		||||
    pid = Ecto.Adapters.SQL.Sandbox.start_owner!(Bump.Repo, shared: not tags[:async])
 | 
			
		||||
    on_exit(fn -> Ecto.Adapters.SQL.Sandbox.stop_owner(pid) end)
 | 
			
		||||
    :ok
 | 
			
		||||
  end
 | 
			
		||||
end
 | 
			
		||||
							
								
								
									
										39
									
								
								test/support/conn_case.ex
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										39
									
								
								test/support/conn_case.ex
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,39 @@
 | 
			
		||||
defmodule BumpWeb.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 BumpWeb.ConnCase, async: true`, although
 | 
			
		||||
  this option is not recommended for other databases.
 | 
			
		||||
  """
 | 
			
		||||
 | 
			
		||||
  use ExUnit.CaseTemplate
 | 
			
		||||
 | 
			
		||||
  using do
 | 
			
		||||
    quote do
 | 
			
		||||
      # Import conveniences for testing with connections
 | 
			
		||||
      import Plug.Conn
 | 
			
		||||
      import Phoenix.ConnTest
 | 
			
		||||
      import BumpWeb.ConnCase
 | 
			
		||||
 | 
			
		||||
      alias BumpWeb.Router.Helpers, as: Routes
 | 
			
		||||
 | 
			
		||||
      # The default endpoint for testing
 | 
			
		||||
      @endpoint BumpWeb.Endpoint
 | 
			
		||||
    end
 | 
			
		||||
  end
 | 
			
		||||
 | 
			
		||||
  setup tags do
 | 
			
		||||
    pid = Ecto.Adapters.SQL.Sandbox.start_owner!(Bump.Repo, shared: not tags[:async])
 | 
			
		||||
    on_exit(fn -> Ecto.Adapters.SQL.Sandbox.stop_owner(pid) end)
 | 
			
		||||
    {:ok, conn: Phoenix.ConnTest.build_conn()}
 | 
			
		||||
  end
 | 
			
		||||
end
 | 
			
		||||
							
								
								
									
										51
									
								
								test/support/data_case.ex
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										51
									
								
								test/support/data_case.ex
									
									
									
									
									
										Normal file
									
								
							@@ -0,0 +1,51 @@
 | 
			
		||||
defmodule Bump.DataCase do
 | 
			
		||||
  @moduledoc """
 | 
			
		||||
  This module defines the setup for tests requiring
 | 
			
		||||
  access to the application's data layer.
 | 
			
		||||
 | 
			
		||||
  You may define functions here to be used as helpers in
 | 
			
		||||
  your tests.
 | 
			
		||||
 | 
			
		||||
  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 Bump.DataCase, async: true`, although
 | 
			
		||||
  this option is not recommended for other databases.
 | 
			
		||||
  """
 | 
			
		||||
 | 
			
		||||
  use ExUnit.CaseTemplate
 | 
			
		||||
 | 
			
		||||
  using do
 | 
			
		||||
    quote do
 | 
			
		||||
      alias Bump.Repo
 | 
			
		||||
 | 
			
		||||
      import Ecto
 | 
			
		||||
      import Ecto.Changeset
 | 
			
		||||
      import Ecto.Query
 | 
			
		||||
      import Bump.DataCase
 | 
			
		||||
    end
 | 
			
		||||
  end
 | 
			
		||||
 | 
			
		||||
  setup tags do
 | 
			
		||||
    pid = Ecto.Adapters.SQL.Sandbox.start_owner!(Bump.Repo, shared: not tags[:async])
 | 
			
		||||
    on_exit(fn -> Ecto.Adapters.SQL.Sandbox.stop_owner(pid) end)
 | 
			
		||||
    :ok
 | 
			
		||||
  end
 | 
			
		||||
 | 
			
		||||
  @doc """
 | 
			
		||||
  A helper that transforms changeset errors into a map of messages.
 | 
			
		||||
 | 
			
		||||
      assert {:error, changeset} = Accounts.create_user(%{password: "short"})
 | 
			
		||||
      assert "password is too short" in errors_on(changeset).password
 | 
			
		||||
      assert %{password: ["password is too short"]} = errors_on(changeset)
 | 
			
		||||
 | 
			
		||||
  """
 | 
			
		||||
  def errors_on(changeset) do
 | 
			
		||||
    Ecto.Changeset.traverse_errors(changeset, fn {message, opts} ->
 | 
			
		||||
      Regex.replace(~r"%{(\w+)}", message, fn _, key ->
 | 
			
		||||
        opts |> Keyword.get(String.to_existing_atom(key), key) |> to_string()
 | 
			
		||||
      end)
 | 
			
		||||
    end)
 | 
			
		||||
  end
 | 
			
		||||
end
 | 
			
		||||
		Reference in New Issue
	
	Block a user