ream88

ream88

Hey,

I’m currently trying to DRY up some tests which have a lot of boilerplate code in the form of:

test "user is updated", %{user_id: user_id} do
  pid = spawn(fn ->
    EventStore.subscribe(UserUpdated)
    assert_receive event = %UserUpdated{aggregate_id: ^user_id}
    EventStore.acknowledge(event)
  end)

  ref = Process.monitor(pid)

  # the actual test

   assert_receive {:DOWN, ^ref, _, _, _}
end

Basically I’m checking if the event UserUpdated is fired in our custom event_store. I tried to implement a custom macro like this:

defmacro assert_event(event, do: block) do
  quote do
    pid =
      spawn(fn ->
        EventStore.subscribe(unquote(event).__struct__)
        assert_receive event = unquote(event)
        EventStore.acknowledge(event)
      end)

    ref = Process.monitor(pid)

    unquote(block)

    assert_receive {:DOWN, ^ref, _, _, _}
  end
end

Which can then be used like this:

test "user is updated", %{user_id: user_id} do
  assert_event %UserUpdated{aggregate_id: user_id} do
    # the actual test
  end
end

But this results in the following warning:

warning: variable “user_id” is unused (there is a variable with the same name in the context, use the pin operator (^) to match on it or prefix this variable with underscore if it is not meant to be used)

But pinning user_id results in the following error:

cannot use ^user_id outside of match clauses

So, my question is (after reading the complicated source code of assert_receive), is there a way to mark some code as a pattern and just forward it to the assert_receive macro inside my custom assert_event macro?

Showing Posts 1 to 4

stefanchrobot

stefanchrobot

Why not keep it simple and use a function?

def assert_event(%event_mod{} = event, func) do
  pid = spawn(fn ->
    EventStore.subscribe(event_mod)
    assert_receive ^event
    EventStore.acknowledge(event)
  end)

  ref = Process.monitor(pid)

  func.()

  assert_receive {:DOWN, ^ref, _, _, _}
end
ream88

ream88 OP

Yeah, a function would have been sufficient, I think I just got carried away with the nicer syntax with a do block instead of an inline func (sorry, still a lot of Ruby influences here :wink:). However the problem still persists. I cannot forward the match to the function. The problem is, I need to work with a match here, as I don’t know all the data inside the emitted event, and therefore can’t use a simple == comparison.

LostKobrakai

LostKobrakai

Pattern matches are a compile time structure in code. You cannot „pass“ a pattern at runtime, so the only way to do it is using macros. When using macros you‘ll need to read up on macro hygine, so variables within generated code become accessible to code not being generated.

ream88

ream88 OP

Yeah, that’s probably the topic I will have to deep dive into :blush: Thx a lot!

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
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
kszambelanczyk
Hello! Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app. I creat...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
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
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
ryanwinchester
apply_graft/2 doesn’t rewrite an add_many sub-workflow’s deps on an add step. Grafted jobs cancel with “upstream job was deleted” Version...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
garrison
Hobbes is a low-level distributed database for the Elixir programming language. Hobbes provides a simple, safe, and scalable storage lay...
New
marciok
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
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews