do anyone know how can i test if the user enters the wrong credentials then he’ll be redirected to the sign in and the error message will show up?
I cannot use any render submit or click in ash authentication so please advise.
ntamer
0
zachdaniel
Creator of Ash
It is a liveview authentication form, so if the user enters the wrong credentials they are not redirected, but an error appears below the input. However you would test that normally in Phoenix Liveview is how you’d test it for AshAuthentication as well.
0
ntamer
Thank you for the quick reply! I’m trying to test it by the normal way but it keeps telling me that the button of the sign in has no phx-click. Does that mean that I shouldn’t use render-click or what?
0
zachdaniel
Creator of Ash
IIRC there is a different helper for testing form submission. The button has no phx-click because it is a submit button on a form. I haven’t written live view form test lately, but if memory serves there is a tool like render_submit that you are looking for 
1
sodapopcan
Are there still plans for adding helpers to the generator for this? If not, it would be nice to add these examples to the docs under testing as this was a bit of a frustrating experience learning how to do this. It’s nice because I know a bit more about AshAuthentication now but it was a pain since I was really excited about the LiveView I was working on and wanted to test it.
I would be happy to do a PR for docs. If so, I’m still a bit confused as only @brunoripa’s answer worked for me. I’m not sure if things changed or I’m Ashing wrong, but my MyApp.Accounts does not have a create function and using Ash.create! results in a policy error.
1
zachdaniel
Creator of Ash
@brunoripa’s answer is effectively the correct one. You don’t necessarily have to use the sign in action logic, as you could do:
user = Ash.Seed.seed!(%User{email: "email", hashed_password: "hashed_password"})
conn
|> Phoenix.ConnTest.init_test_session(%{})
|> store_in_session(user)
A PR to add this to the docs would be much appreciated 
2
sodapopcan
Oh ya, I was trying to use seeds (which would be my preference) but couldn’t get it to work. I’m assuming you still have to call the sign in, logic no? I still can’t get it to work with your example—I get bad password (I manually called Bcrypt.hash_pwd_salt("Password12345")). I can make a PR and discuss it there, though.
EDIT: Oops, don’t mind me, it does indeed work! 
0
aidalgol
Just want to add that this worked for me, while this earlier solution did not.
I’m not sure why, but the one that works more closely matches what my AuthController is doing.
0
joelparkerhenderson
# How to test Elixir Phoenix Ash Authentication Magic Link LiveView.
#
# This example is developed for a typical resource "User" and "Item",
# and uses AshAuthentication with a default setup of user email address.
# Modify this example as you wish for your own needs and settings.
#
# I appreciate contructive feedback and advice on how to improve this.
# And I'm happy to answer questions. Email joel@joelparkerhenderson.com.
#
# This file is /test/my_app_web/controllers/items_test.exs
defmodule MyAppWeb.ItemsTest do
import Phoenix.LiveViewTest
use MyAppWeb.ConnCase
alias MyApp.Accounts.User
defp my_user() do
User
|> Ash.Changeset.for_create(:create, %{email: "example@example.com"})
|> Ash.create(upsert?: true, upsert_identity: :unique_email)
end
defp my_sign_in(user) do
strategy = AshAuthentication.Info.strategy!(User, :magic_link)
{:ok, token} = AshAuthentication.Strategy.MagicLink.request_token_for(strategy, user)
AshAuthentication.Strategy.action(strategy, :sign_in, %{"token" => token})
end
setup %{conn: conn} do
{:ok, user} = my_user()
{:ok, user} = my_sign_in(user)
conn =
conn
|> Phoenix.ConnTest.init_test_session(%{})
|> AshAuthentication.Plug.Helpers.store_in_session(user)
{:ok, conn: conn}
end
test "index", %{conn: conn} do
conn = get(conn, ~p"/items")
response = html_response(conn, 200)
assert response =~ "Items"
end
end
1