phoenix_ecto

Phoenix and Ecto integration with support for concurrent acceptance testing

Latest version: 4.4.0 registry icon
Maintenance score
31
Safety score
100
Popularity score
78
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
Security
  Vulnerabilities
Version Suggest Low Medium High
4.4.0 0 0 0 0
4.3.0 0 0 0 0
4.2.1 0 0 0 0
4.2.0 0 0 0 0
4.1.0 0 0 0 0
4.0.0 0 0 0 0
3.6.0 0 0 0 0
3.5.0 0 0 0 0
3.4.0 0 0 0 0
3.3.0 0 0 0 0
3.2.3 0 0 0 0
3.2.2 0 0 0 0
3.2.1 0 0 0 0
3.2.0 0 0 0 0
3.1.0 0 0 0 0
3.1.0-rc.0 0 0 0 0
3.0.1 0 0 0 0
3.0.0 0 0 0 0
3.0.0-rc.0 0 0 0 0
2.0.3 0 0 0 0
2.0.2 0 0 0 0
2.0.1 0 0 0 0
2.0.0 0 0 0 0
1.2.0 0 0 0 0
1.1.0 0 0 0 0
1.0.0 0 0 0 0
0.9.0 0 0 0 0
0.8.1 0 0 0 0
0.8.0 0 0 0 0
0.7.0 0 0 0 0
0.6.0 0 0 0 0
0.5.0 0 0 0 0
0.4.0 0 0 0 0
0.3.2 0 0 0 0
0.3.1 0 0 0 0
0.3.0 0 0 0 0
0.2.0 0 0 0 0
0.1.0 0 0 0 0

Stability
Latest release:

4.4.0 - this version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant



Phoenix/Ecto

Action Status

A project that integrates Phoenix with Ecto, implementing all relevant protocols.

Installation

You can install phoenix_ecto by adding it to your list of dependencies in mix.exs:

def deps do
  [{:phoenix_ecto, "~> 4.0"}]
end

The Phoenix <-> Ecto integration

Thanks to Elixir protocols, the integration between Phoenix and Ecto is simply a matter of implementing a handful of protocols. We provide the following implementations:

  • Phoenix.HTML.FormData protocol for Ecto.Changeset
  • Phoenix.HTML.Safe protocol for Decimal
  • Plug.Exception protocol for the relevant Ecto exceptions

Concurrent browser tests

This library also provides a plug called Phoenix.Ecto.SQL.Sandbox that allows developers to run acceptance tests powered by headless browsers such as ChromeDriver and Selenium concurrently. If you are not familiar with Ecto's SQL sandbox, we recommend you to first get acquainted with it by reading Ecto.Adapters.SQL.Sandbox documentation.

To enable concurrent acceptance tests, make sure you are using PostgreSQL and follow the instructions below:

  1. Set a flag to enable the sandbox in config/test.exs:

    config :your_app, sql_sandbox: true
  2. And use the flag to conditionally add the plug to lib/your_app/endpoint.ex:

    if Application.get_env(:your_app, :sql_sandbox) do
      plug Phoenix.Ecto.SQL.Sandbox
    end

    Make sure that this is placed before the line plug YourApp.Router (or any other plug that may access the database).

You can now checkout a sandboxed connection and pass the connection information to an acceptance testing tool like Hound or Wallaby.

Hound

To write concurrent acceptance tests with Hound, first add it as a dependency to your mix.exs:

{:hound, "~> 1.0"}

Make sure to start it at the top of your test/test_helper.exs:

{:ok, _} = Application.ensure_all_started(:hound)

Then add the following to your test case (or case template):

use Hound.Helpers

setup tags do
  pid = Ecto.Adapters.SQL.Sandbox.start_owner!(YourApp.Repo, shared: not tags[:async])
  on_exit(fn -> Ecto.Adapters.SQL.Sandbox.stop_owner(pid) end)
  metadata = Phoenix.Ecto.SQL.Sandbox.metadata_for(YourApp.Repo, pid)
  Hound.start_session(metadata: metadata)
  :ok
end

Hound supports multiple drivers like Chrome, Firefox, etc but it does not support concurrent tests under PhantomJS (the default).

Wallaby

To write concurrent acceptance tests with Wallaby, first add it as a dependency to your mix.exs:

{:wallaby, "~> 0.25", only: :test}

Wallaby can take care of setting up the Ecto Sandbox for you if you use use Wallaby.Feature in your test module.

defmodule MyAppWeb.PageFeature do
  use ExUnit.Case, async: true
  use Wallaby.Feature

  feature "shows some text", %{session: session} do
    session
    |> visit("/home")
    |> assert_text("Hello world!")
  end
end

If you don't use Wallaby.Feature, you can add the following to your test case (or case template):

use Wallaby.DSL

setup tags do
  pid = Ecto.Adapters.SQL.Sandbox.start_owner!(YourApp.Repo, shared: not tags[:async])
  on_exit(fn -> Ecto.Adapters.SQL.Sandbox.stop_owner(pid) end)
  metadata = Phoenix.Ecto.SQL.Sandbox.metadata_for(YourApp.Repo, pid)
  {:ok, session} = Wallaby.start_session(metadata: metadata)
end

Wallaby currently supports ChromeDriver and Selenium, allowing testing in almost any browser.

Configuration

The Plug.Exception implementations for Ecto exceptions may be disabled by including the error in the mix configuration.

config :phoenix_ecto,
  exclude_ecto_exceptions_from_plug: [Ecto.NoResultsError]

Copyright and License

Copyright (c) 2015, Chris McCord.

Phoenix/Ecto source code is licensed under the MIT License.