allanegidio
Howdy
I’ve been having some problems to test async_nolink function.
My mount have a function like that:
Task.Supervisor.async_nolink(TaskSupervisor, fn ->
Accounts.get_dashboard(user.id)
end)
And I have a handle_info like that:
def handle_info({task_ref, dashboard_data}, socket) do
Process.demonitor(task_ref, [:flush])
{:noreply, assign(socket, dashboard_data)}
end
It is working pretty well but when I test and send my message like that:
{:ok, live, _html} = live(conn, ~p"/")
send(live.pid, {task_ref?, %{total_users: 100}})
What I should put inside my task_ref during tests?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
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
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
adw632
You can’t do it like that as the live view process is getting a process monitor when it starts the Task using the task supervisor. That is why it demonitors it once it gets the Account results.
You can probably use Mock for the Accounts.get_dashboard() call to return the canned response and all the process messaging will work the same.
allanegidio
Hmmm I got it
When I tried this approach I had to add a Process.sleep to the test have time to get the data and to be able to do the asserts.
Thanks to share your thoughts
JohnnyCurran
If you want to do asynchronous assigns, you should probably be using assign_async
More info:
allanegidio
Beautiful.
It worked so well thank you!