chensan

chensan

I’m writing tests for my controller:

  defp log_in_user(%{conn: conn, log_in_as: email}) do
    role = role_fixture()
    user = user_fixture(role, email: email)
    conn = assign(conn, :current_user, user)
    {:ok, conn: conn, user: user}
  end

  defp create_site(%{conn: conn, user: user}) do
    site = site_fixture(user)
    {:ok, site: site}
  end

  describe "delete site" do
    setup [:log_in_user, :create_site]

    @tag log_in_as: "sam"
    test "deletes chosen site", %{conn: conn, site: site} do
      conn = delete(conn, Routes.site_path(conn, :delete, site))
      assert redirected_to(conn) == Routes.site_path(conn, :index)

      assert_error_sent 404, fn ->
        get(conn, Routes.site_path(conn, :show, site))
      end
    end
  end

The weird thing here is conn.assigns.current_user becomes nil in assert_error_sent where it should have value.

I found some similar questions around the web:

  1. Troubleshooting a failed test 302 redirect instead of 200 - #3 by chensan
  2. https://stackoverflow.com/questions/50110449/phoenix-controller-test-case-loses-current-user
  3. https://stackoverflow.com/questions/46363292/losing-conn-assigns-in-the-middle-of-a-test

Seems the problem is caused by Phoenix.ConnTest – Phoenix v1.4.0, and there’s a fix:

      saved_assigns = conn.assigns

      conn =
        conn
        |> recycle()
        |> Map.put(:assigns, saved_assigns)

I don’t quite understand why, it’s so unexpected in our tests. Anyone could help explain it?

Showing Posts 1 to 8

LostKobrakai

LostKobrakai

recycle does essentially what happens if you start a new request in the browser. Any new request in the browser will start of without any assigns. Usually you’re kept logged in by putting something in the session for the user.

chensan

chensan OP

When I logged in a website, I would expect myself logged-in all the time until I log out. But Phoenix recycling breaks this expectation.

LostKobrakai

LostKobrakai

That’s just not true. If you’re not using session based authentication you’d need to log in new for each request. The only data which survives between requests is the stuff you put into the session. Anything else is discarded at the end of a request. That’s true for the request you do with a browser in dev mode and exactly what recycle mimics for tests.

chensan

chensan OP

Ok, so how can I make the tests better? Writing conn = conn |> cycle() |> Map.put(:assigns, conn.assigns) everywhere in my controller tests is so ugly.

idi527

idi527

Maybe Plug.Test — Plug v1.20.2

setup %{conn: conn} do
  {:ok, conn: Plug.Test.init_test_session(conn, user_id: 666)}
end

I wouldn’t change assigns manually, instead I’d pipe the requests through the actual plug pipelines with the session set via Plug.Test.init_test_session/2 to get the expected conn with all relevant assigns set.

LostKobrakai

LostKobrakai

Either what @idi527 said: Use the session and your real plugs / pipelines.
Or simply not reuse the conn for places where you’re e.g. testing a single plug.

result = MyPlug.call(conn, opts)
assert …

result = MyPlug.call(conn, opts_2)
assert …
chensan

chensan OP

Can we say the tip presented in Programming Phoenix book for easier testing is defective :slight_smile:

  def call(conn, _opts) do
    user_id = get_session(conn, :user_id)

    cond do
      conn.assigns[:current_user] ->
        conn

      user = user_id && Accounts.get_user(user_id) ->
        assign(conn, :current_user, user)

      true ->
        assign(conn, :current_user, nil)
    end
  end

In the beginning I just logged in user with naive post(conn, Routes.session_path(conn, :create), ...):

    @tag log_in_as: "sam"
    test "deletes chosen site", %{conn: conn, site: site, user: user} do
      conn =
        post(conn, Routes.session_path(conn, :create),
          session: %{email: user.email, password: "123456"}
        )

      conn = delete(conn, Routes.site_path(conn, :delete, site))
      assert redirected_to(conn) == Routes.site_path(conn, :index)

      # conn =
      #   conn
      #   |> recycle()
      #   |> Map.put(:assigns, conn.assigns)

      assert_error_sent 404, fn ->
        get(conn, Routes.site_path(conn, :show, site))
      end
    end

No need to call recycle() in this code.

chensan

chensan OP

After reading the source code, I’d like to share what I learned so far.

When we run get(conn, Routes.site_path(conn, :show, site)), a new conn was created, and cookies and some request headers (~w(accept authorization)) from old conn are copied to new conn - that’s what Phoenix recycling does for us, it emulates the behavior of browser. But conn.assigns is not copied, results in a nil value of current_user.

The reason post(conn, Routes.session_path(conn, :create), session: %{email: user.email, password: "123456"} ) works is because Auth module selects another path:

  def call(conn, _opts) do
    user_id = get_session(conn, :user_id)

    cond do
      conn.assigns[:current_user] -> # <- the way programming phoenix book suggests
        conn

      user = user_id && Accounts.get_user(user_id) -> # <- post Routes.session_path just selects this way.
        assign(conn, :current_user, user)

      true ->
        assign(conn, :current_user, nil)
    end
  end

Thanks all for your kind help :slight_smile:

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews