Awlexus
Hi, I’m getting the following error message in my tests, and I’m not sure where they come from. I can’t see any difference to Tesla.Mock — tesla v1.20.0, except for async: true, but setting that to false doesn’t change anything.
I have other tests in the same project that also use Tesla.Mock, which don’t have this problem, and I couldn’t find a difference there either. Mocking works when I use mock_global and async: false, but that breaks a lot of other testcases, so that’s not an option.
I have 2 tests that fail because of this. They both reference the same process #PID<0.902.0> in the error message
Any help would be appreciated. Thanks
above_mock: #PID<0.914.0>
above_post: #PID<0.914.0>
1) test ... (...)
test/my_app/redacted_test.exs:292
** (Tesla.Mock.Error) There is no mock set for process #PID<0.902.0>.
Use Tesla.Mock.mock/1 to mock HTTP requests.
See https://github.com/teamon/tesla#testing
stacktrace:
(tesla 1.8.0) lib/tesla/mock.ex:206: Tesla.Mock.call/2
(tesla 1.8.0) lib/tesla/middleware/timeout.ex:59: anonymous fn/1 in Tesla.Middleware.Timeout.safe_async/2
(elixir 1.15.7) lib/task/supervised.ex:101: Task.Supervised.invoke_mfa/2
(elixir 1.15.7) lib/task/supervised.ex:36: Task.Supervised.reply/4
# config
config :tesla, adapter: Tesla.Mock
# Test file
def MyApp.RedactedTest do
use MyApp.DataCase, async: true
import Tesla.Mock
setup :general_setup
describe "describe" do
test "..." do
IO.inspect(self(), label: :above_mock)
mock(fn _ -> json(%{translations: []}) end)
call_tesla_deep_in_this_function()
end
end
end
# Implementation
defmodule MyApp.Client do
def client(opts) do
middlewares = [...]
Tesla.client(middlewares)
end
def call_service(client, body) do
IO.inspect(self(), label: :above_post)
Tesla.post(client, "path", body)
end
end
# call_service is called like this
client = Client.client([...])
body = "body here"
Client.call_service(client, body)
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
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
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
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
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
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex











Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
JohnnyCurran
Is the code under test performing the http request from a
Taskor from aGenServer? Those process pids will not have the Tesla mocked call available to them.I have solved this with a combo of
mock_globalandasync: falsein the test file. This means it doesn’t step on my async tests. You will need to use bothmock_globalandasync: falseon each test file where this error appears if you are unable (or don’t want to due to requirements) refactor the http call to happen in a different processAwlexus
There is no
TaskorGenServerinvolved. The first 2 lines of my code block show that the mock and the http request happen in the same process. It’s deeply nested, but it happens immediately after.JohnnyCurran
Can you up your stack trace length / post the full stack trace? It seems like the mock call is coming from a task:
Awlexus
Unfortunately, this already is the full stack track provided by the test. I didn’t touch the default values of the length, so it should already be the whole stack trace