That answers my question, thank you!
And thank you again for the book 
tjdam
mstibbard
Some errata for you 
In chapter 8 (authentication) during refactoring you move import ChatterWeb.ConnTestHelpers into ChatterWeb.ConnCase but your example code highlights the wrong thing as being added (import Chatter.Factory)
At the end of chapter 9 (creating users) if you run the server and try to create a user you will get the following error despite all tests passing.
[debug] Processing with ChatterWeb.SessionController.create/2
Parameters: %{"_csrf_token" => "AWNgFCMXGTFbTTM4MTwCITsMDzkwCCdQw-TpIomu4yZusykgM9PifMb2", "email" => "test@test.com", "password" => "[FILTERED]"}
Pipelines: [:browser]
[debug] QUERY OK source="users" db=0.8ms queue=1.3ms idle=1252.9ms
SELECT u0."id", u0."email", u0."hashed_password", u0."session_secret", u0."inserted_at", u0."updated_at" FROM "users" AS u0 WHERE (u0."email" = $1) ["test@test.com"]
[info] CONNECTED TO ChatterWeb.UserSocket in 51µs
Transport: :websocket
Serializer: Phoenix.Socket.V2.JSONSerializer
Parameters: %{"vsn" => "2.0.0"}
[info] Sent 500 in 203ms
[error] #PID<0.914.0> running ChatterWeb.Endpoint (connection #PID<0.903.0>, stream id 3) terminated
Server: localhost:4000 (http)
Request: POST /sessions
** (exit) an exception was raised:
** (UndefinedFunctionError) function nil.id/0 is undefined
nil.id()
(doorman 0.6.2) lib/login/session.ex:12: Doorman.Login.Session.login/2
(chatter 0.1.0) lib/chatter_web/controllers/session_controller.ex:11: ChatterWeb.SessionController.create/2
(chatter 0.1.0) lib/chatter_web/controllers/session_controller.ex:1: ChatterWeb.SessionController.action/2
(chatter 0.1.0) lib/chatter_web/controllers/session_controller.ex:1: ChatterWeb.SessionController.phoenix_controller_pipeline/2
(phoenix 1.5.6) lib/phoenix/router.ex:352: Phoenix.Router.__call__/2
(chatter 0.1.0) lib/chatter_web/endpoint.ex:1: ChatterWeb.Endpoint.plug_builder_call/2
(chatter 0.1.0) lib/plug/debugger.ex:132: ChatterWeb.Endpoint."call (overridable 3)"/2
(chatter 0.1.0) lib/chatter_web/endpoint.ex:1: ChatterWeb.Endpoint.call/2
(phoenix 1.5.6) lib/phoenix/endpoint/cowboy2_handler.ex:65: Phoenix.Endpoint.Cowboy2Handler.init/4
(cowboy 2.8.0) /home/matt/prog/chatter/deps/cowboy/src/cowboy_handler.erl:37: :cowboy_handler.execute/2
(cowboy 2.8.0) /home/matt/prog/chatter/deps/cowboy/src/cowboy_stream_h.erl:300: :cowboy_stream_h.execute/3
(cowboy 2.8.0) /home/matt/prog/chatter/deps/cowboy/src/cowboy_stream_h.erl:291: :cowboy_stream_h.request_process/3
(stdlib 3.13.2) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
0
germsvel
Thanks for letting me know about these. I’ll update the syntax highlighting for the first, and look into what might be causing the second.
0
triad
Thank you for sharing your work.
Do you recommend this for new folks (with some programming experience) as well?
0
slouchpie
mstibbard
germsvel
Hi @triad,
Do you recommend this for new folks (with some programming experience) as well?
I think it depends. I don’t cover a lot of topics in depth because I assume prior knowledge of Elixir and Phoenix.
That being said, if you already have prior programming experience, and you’re comfortable looking for documentation on things not covered, it could be a good way to learn Phoenix. It seems like others here think so too, so it might be worth a shot.
If you give it a try, I’d love to hear your thoughts on it.
0
dbaer
This is really awesome, thank you for posting! I only wish I had started my current project with this methodology, I think it would have massively improved my testing flow.
My current branch has almost 400 tests, and that’s not even the bare minimum i should have to fully cover the logic bearing code. It is as much of a nightmare as one could expect.
1
bdarla
I really enjoyed the accuracy in guiding the setup procedure! Thank you for this great help!
A little detail that some Mac users may face, which is related with the latest Mac OS versions is when getting the following error:
“chromedriver” cannot be opened because the developer cannot be verified.
I have addressed this issue by running:
xattr -d com.apple.quarantine <pathto/chromedriver>
I am not sure if it is safe in general, but I trusted that chromedriver in particular is not dangerous.
1
germsvel
I finally got a chance to look into this. I realized that in the authentication chapter, we never test the case when someone enters an incorrect email/password combination.
So the error you saw happens because we’re assuming that Doorman.authenticate(email, password) returns a user. But if the email or password are incorrect, it returns nil, so we get a call to nil.id` later.
Thanks for catching this. I’ll have to update the Authentication chapter to test that case.
1