axelclark
I’ve added Pow into my project for authentication. Now I’m trying to update the tests Phoenix generated when I created my contexts.
I’ve added all my resource routes to the protected pipeline.
I used Pow.Plug.assign_current_user/3 to add a current user to my conn.
test "redirects to show when data is valid", %{conn: conn} do
user = %Golf.Accounts.User{email: "test@example.com", id: 1}
conn = Pow.Plug.assign_current_user(conn, user, [])
conn = post(conn, Routes.course_path(conn, :create), course: @create_attrs)
assert %{id: id} = redirected_params(conn)
assert redirected_to(conn) == Routes.course_path(conn, :show, id)
conn = get(conn, Routes.course_path(conn, :show, id))
assert html_response(conn, 200) =~ "Show Course"
end
My assertions about the create action all pass.
assert %{id: id} = redirected_params(conn)
assert redirected_to(conn) == Routes.course_path(conn, :show, id)
However, the final show action
conn = get(conn, Routes.course_path(conn, :show, id))
assert html_response(conn, 200) =~ "Show Course"
fails because it gets redirected to the new_session path:
** (RuntimeError) expected response with status 200, got: 302, with body:
<html><body>You are being <a href="/session/new?request_path=%2Fcourses">redirected</a>.</body></html>
If I reuse the original conn after I assign the current user, but before the create action, my tests pass.
test "redirects to show when data is valid", %{conn: conn} do
user = %Golf.Accounts.User{email: "test@example.com", id: 1}
new_conn = Pow.Plug.assign_current_user(conn, user, [])
conn = post(new_conn, Routes.course_path(new_conn, :create), course: @create_attrs)
assert %{id: id} = redirected_params(conn)
assert redirected_to(conn) == Routes.course_path(conn, :show, id)
conn = get(new_conn, Routes.course_path(new_conn, :show, id))
assert html_response(conn, 200) =~ "Show Course"
end
Can someone help me out with how I need to update my tests?
Thanks!
Axel
Trending in Questions
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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
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
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
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
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
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security











Showing Posts 5 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
juanma1331
Fixed. Had to recycle the conn manually.
All the tests are passing now, but i have defined the recycle_conn function on the controller_test, what if i want to test another authed controller? Need to redefine again, or create another helper module and define it there to ease reuse.
Im pretty new to elixir/phoenix and web dev in general. Sorry for my english
juanma1331
Hi, After adding Pow, I has 9 test failing, after placing the setup macro to add the user to the conn i has 3 tests that keep failing with error.
If i remove :protected from pipeline on the scope all test pass. So it has to be something with the authentication. Thanks
danschultzer
Yeah, you would only ever need to do that if you are testing the session controller itself. Assigning
:current_useris sufficient for all other controllers/routes.dimitarvp
If I am reading this thread right, there’s no point to have a test that does a POST and validates that Pow successfully authenticates a user then?
danschultzer
Your second example is the way to go. This could also be done in a
setupmacro like so:It’s because of how phoenix recycles connections in tests. The response conn will have a
:statekey set to:sentso when it’s reused the test helpers in Phoenix will build a new connection and only copy over headers e.g. cookies. Assigns will not be preserved.