sergio
I wrote a doctest that tests that the function is returning a %Foobar.Accounts.User struct type.
1) test doc at Foobar.Accounts.create_user_with_email_only/1 (1) (Foobar.AccountsTest)
test/accounts/accounts_test.exs:3
Doctest failed
code: Foobar.Accounts.create_user_with_email_only("test@email.com") === {:ok, %Foobar.Accounts.User{}}
left: {:ok,
%Foobar.Accounts.User{__meta__: #Ecto.Schema.Metadata<:loaded, "users">,
confirmation_code: "338128", email: "test@email.com",
email_confirmed: false, encrypted_password: nil, fullname: nil,
id: 2306, inserted_at: ~N[2017-07-25 03:26:15.407053],
invite_token: nil, onboarded: false, password: nil, pin: nil,
roles: nil,
team: #Ecto.Association.NotLoaded<association :team is not loaded>,
team_id: nil, token: "flDJRP6Vx78pI3uSOgSVPb2HxcEZ3DYU",
updated_at: ~N[2017-07-25 03:26:15.413361], username: nil}}
stacktrace:
lib/accounts/accounts.ex:15: Foobar.Accounts (module)
My doctests look like:
@doc """
Create a user with only the email field set. The user is not
associated with any team.
## Examples
iex> Foobar.Accounts.create_user_with_email_only("test@email.com")
{:ok, %Foobar.Accounts.User{}}
iex> Foobar.Accounts.create_user_with_email_only("")
{:error, "Email cannot be blank or nil."}
iex> Foobar.Accounts.create_user_with_email_only(nil)
{:error, "Email cannot be blank or nil."}
"""
def create_user_with_email_only(email) when byte_size(email) > 0 do
Thanks for the help!
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Hi all, I’m new here and would like to hear peoples views on my Elixir/Phoenix based game-engine! :smiley:
Mutonex gamedesign was finish...
New
Hello
I’ve been coding in Elixir for almost two years now because of my current job where we implemented Elixir in our application. But ...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
mudasobwa
Doctest does not pattern match result, it explicitly compares it against pinned value:
That said, you should retrieve the result and assert the explicit pattern match:
meddle
Another idea similar to the above without the use of
with. But I really like the idea withwithtoomudasobwa
This has a drawback: is the test fails, there would be a messy message;
with-approach will respond with smth like “expected:passed, got …” putting out to the screen the actual result (due to howwithworks.)meddle
Ah, I see your point. And the idea with
withis not really much complex or long. So yeah thewithidea is better.