How do I test a LiveView hook triggered by a Stripe form?

think you’ll need to test using something like wallaby eg headless chrome/firefox.. since this requires a js runtime..

you can see https://www.tddphoenix.com for getting started - excellent resource..

could be wrong though, but don’t see how elixir side should/can know what goes on in js hooks..

Something like that is definitely an option, but I’m hoping there’s a way to just trigger the event within a LiveView test in elixir. There’s no way to invoke the Stripe form or fill it out without a tool like wallaby, but it seems like there ought to be a way to simulate the this.pushEvent call that would normally happen on the form submit.

The closest I’ve been able to get so far is setting up a handle_info function that works the same way handle_event does and testing that, because with handle_info, I can trigger it in the test like this

send(view.pid, {:test_save_card, "some stripe token"})

and if my setup looks like this

  def handle_event("save-card", %{"token" => stripe_token}, socket) do
    save_card(stripe_token, socket)
  end

  def handle_info({:test_save_card, stripe_token}, socket) do
    save_card(stripe_token, socket)
  end

then when handle_info tests pass, it should be a good bet that handle_event tests, if they were possible to write, would pass the same way. It’s hacky, but it basically works. Unfortunately, as far as I can tell, there’s no analog to send(view.pid, {:test_save_card, "some stripe token"}) that works to trigger handle_event.

If you have the socket in the test (I haven’t written any tests with liveview, but I imagine you have?) you can just call YourLiveView.Module.handle_event("save-card", %{"token" => "your_token"}, the_socket) and assert on the result of save card and any side effects?

This doesn’t test the client interface tough, just that if an event "save-card" with those params are sent through the live view it works correctly.

Yes, I think this might work, but so far I haven’t been able to figure out how to get access to the socket in tests, either

Yeah probably it’s possible to build the socket manually but I didn’t see any helpers for that while giving it a quick glance. I thought it would allow as it does with channels (the phx channelcase) you have some helpers to build it though.

Just FYI: There’s the render_hook/3 option now, which simulates sending an event through this.pushEvent("foo", "bar") in your JavaScript. It will then trigger the handle_event("foo", "bar", socket)-callback in your LiveView.

So, in your use case, you could write a test like:

render_hook(view, "save-card", %{"token" => stripe_token})

That works perfectly; thank you!

I’d still like to know how to access the socket. I have a handle_event that gets called from the browser when a user releases the mouse button after drawing a box on an image.

My handle_event saves the latest coordinates in the assigns and then fires back all the boxes that the user has drawn to the browser to re-render them in JavaScript. I’d love to be able to assert that the assigns has the right data after processing what came back from the browser on mouseup.

Someone know how to test pushEventTo when targeting component ? render_hook/3 requires that component has the phx-hook on the target component however in my case i have the div with phx-hook outside and it uses the pushEventTo("from", ...) to update crop zone in real time. It is a multi file upload where user before uploading can crop all images in order to select required zone with correct aspect. So to test it i need to execute the handle_event on my FormComponent.
And when i do

      view
      |> element("form")
      |> render_hook("update-crop", %{crop_map: ...})

I have error that element selected by "form" does not have phx-hook attribute. which is true of course because hook is outside.

I have something like that :

  <%= for entry <- @uploads.image_file.entries do %>
      <div phx-hook="CropperComponent" phx-update="ignore" id={"Cropper-#{entry.uuid}"}>
        <%= live_img_preview entry %>
        ...
      </div>
    </div>
  <% end %>

  <.form let={f} for={@changeset} phx-target={@myself} phx-change="validate" phx-submit="save">
     ....
     <%= submit "Save" %>
  </.form>

Bit of a late answer, but could potentially help someone coming across this post :

You need to target the element with phx-hook attached to it. In your case it would be the div(s) you perform the iteration on.

Also, if your code resides in a Live Component and you don’t want the pushEventTo to be sent to the parent, you need to add a phx-target={@myself} on the targetted element.