How to test a Phoenix application with Bypass?

Fl4m3Ph03n1x

Background

I have a Phoenix application, freshly created. This app has an endpoint that makes a request to an external service, and I would like to exercise/test the entire stack vertically.

To achieve this I have opted to try bypass to mock responses from the external service.

What I tried

To achieve this I have come up with the following code:

defmodule MyApp.ApplicationTest do
  @moduledoc false

  use ExUnit.Case, async: false

  alias HTTPoison

  @external_service_port 5112

  setup do
    bypass = Bypass.open(port: @external_service_port)

    {:ok, bypass: bypass}
  end

  test "client can handle an error response", %{bypass: bypass} do
    Bypass.expect_once(bypass, "GET", "api/users/validate", fn conn ->
      Plug.Conn.resp(conn, 429, ~s<{"errors": [{"code": 88, "message": "Rate limit exceeded"}]}>)
    end)

    MyApp.Application.start(nil, nil) |> IO.inspect(label: "APPLICATION STARTUP")

    HTTPoison.get("http://localhost:4000/api/users/validate") |> IO.inspect(label: "REQUEST")
  end
end

Problem

Unfortunately, when I run the test this is the output I get:

❯ mix test test/my_app/application_test.exs 
APPLICATION STARTUP: {:error, {:already_started, #PID<0.404.0>}}
REQUEST: {:error, %HTTPoison.Error{reason: :econnrefused, id: nil}}

My understanding is that the application is already started, but somehow I cannot reach it and I don’t know why.

Questions

Is this the correct way to exercise the entire stack using ByPass with Phoenix?
Is there a better way of testing this?
Why can’t I access my application?

12 comments

/phoenix #testing #endpoint #bypass

0 1154 12

2024-06-13 11:53:02 UTC

Showing Posts 1 to 10

Show Best Posts
Show All (oldest first)
Show All (newest first)

fuelen

You don’t need to start MyApp.Application manually. mix does this for you. Check mix.exs file, probably it has something like this:

def application do
  [
    mod: {MyApp.Application, []},
    # ...
  ]
end

Bypass started a server using port 5112, but you’re making requests to 4000

Post #1

Fl4m3Ph03n1x

I am confused then. My objective is to use bypass to simulate the response from the external service (which uses port 5112). Port 4000 is the default port for when I use mix phx.server.

Does this mean that both my application (usually at port 4000) and the external service I am trying to simulate, are both in port 5112?

If so, how do I make bypass distinguish between them?

Post #2

mudasobwa

Creator of Cure

bypass obviously cannot mock external ports, it injects a plug into your server pipeline, that’s it.

Post #3

Fl4m3Ph03n1x

So, this means I cannot use bypass to mock responses from an external service while also using HTTTPoison to directly call my application, correct?

The best I could do is to directly call the validate function in MyApp.ValidateController and then use bypass to mock the response from the external service said controller would eventually call, right?

Post #4

mudasobwa

Creator of Cure

I am not sure I see any advantage of using bypass over mox here.

I would do the following: mock HTTPoison.Base behaviour with mox. Make an HTTP client configurable, and point the configuration to your Mox module for HTTPoison in test env, and to HTTPoison otherwise. Do return whatever you want from the mocks.

Post #5

nivanson

I’ve been using test_server for this purpose. It’s not perfect but it is pretty good.

See GitHub - danschultzer/test_server: No fuzz ExUnit test server to mock third party services · GitHub

Post #6

Fl4m3Ph03n1x

Isn’t this the same as bypass?
Meaning, if I use testserver I will not be able to call my app’s endpoints while simulating the third party, correct?

Post #7

ananthakumaran

Bypass starts an HTTP server, it doesn’t mock anything. I think OP’s issue is about using HTTPoison to hit his own service. This should be done via plug test module.

Post #8

LostKobrakai

One can also test ones own endpoint with an http client, but that requires actually binding the endpoint to a port, which is not the default. Adding server: true for the endpoint in config/test.exs would enable that. I’d only do that for integration tests though, as indeed plug level tests are usually fine and have the better DX especially around thing going wrong.

Post #9

nivanson

I don’t understand what you are asking. Why would you not be able to call your own application server?

You would be running your own server for your application. If your endpoint is running you should be able to hit it as usual. Test server does not change that. It is an entirely different server running on a different port. Your test can hit either your server or the test server.

Post #10

Load more posts (2 remaining)