setop
Hi,
I am maintaining the code base of Mobilizon : an event management platform for the Fediverse ; initially derived from Pleroma.
I’m having trouble with adapting the tests to a very small change.
What I get is :
- test/graphql/resolvers/member_test.exs:226
** (Mox.UnexpectedCallError) no expectation defined for Mobilizon.Service.HTTP.ActivityPub.Mock.call/2
- test/federation/activity_pub/transmogrifier/follow_test.exs:45
** (Mox.UnexpectedCallError) expected Mobilizon.Service.HTTP.ActivityPub.Mock.call/2 to be called once but it has been called 2 time
- test/federation/activity_pub/transmogrifier/undo_test.exs:51
** (Mox.UnexpectedCallError) expected Mobilizon.Service.HTTP.ActivityPub.Mock.call/2 to be called once but it has been called 2 times
- test/federation/activity_pub/transmogrifier/update_test.exs:160
** (Mox.UnexpectedCallError) no expectation defined for Mobilizon.Service.HTTP.ActivityPub.Mock.call/2
But I don’t know what an expectation is in the context of ExUnit and why it is sometimes called twice.
If someone can help me to feel less dumb, it would be really appreciated.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
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
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 2 to 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
fuelen
expectationis not about ExUnit, but about Mox library. If you want to understand this then read this article first Mocks and explicit contracts - Dashbit Blogand then Mox — Mox v1.2.0 to know how to declare new expectations.
al2o3cr
Mobilizon.Service.HTTP.ActivityPubis wired up to a mock inconfig/test.exs:You’ll need a similar stanza to ones like this to handle the
:postrequest thatpublish_onemakes.One thing I do wonder: how was this working before? I haven’t chased down what
inboxtypically is inpublish_onecalls, but were the specs making a real HTTP request?