Difficulty getting Wallaby to connect to Selenium

[aidalgol]

I am trying to add end-to-end testing to my Phoenix application using Wallaby, but Wallaby does not seem to be connecting to Selenium.

This is the error:

  1) feature Log In/Out button is "Log In" (PaddyWeb.LandingPageTest)
     test/paddy_web/end_to_end/landing_page_test.exs:7
     ** (RuntimeError) Wallaby had an internal issue with HTTPoison:
     %HTTPoison.Error{id: nil, reason: :econnrefused}
     stacktrace:
       (wallaby 0.28.0) lib/wallaby/httpclient.ex:50: Wallaby.HTTPClient.make_request/5
       (wallaby 0.28.0) lib/wallaby/selenium.ex:93: Wallaby.Selenium.start_session/1
       (wallaby 0.28.0) lib/wallaby.ex:82: Wallaby.start_session/1
       (wallaby 0.28.0) lib/wallaby/feature.ex:152: Wallaby.Feature.Utils.start_session/2
       (elixir 1.10.4) lib/enum.ex:1400: anonymous fn/3 in Enum.map/2
       (elixir 1.10.4) lib/enum.ex:2116: Enum.map/2
       test/paddy_web/end_to_end/landing_page_test.exs:3: PaddyWeb.LandingPageTest.__ex_unit_setup_0/1
       test/paddy_web/end_to_end/landing_page_test.exs:1: PaddyWeb.LandingPageTest.__ex_unit__/2

Wallaby config in test.exs:

config :wallaby,
  driver: Wallaby.Selenium,
  otp_app: :paddy,
  selenium: [
    remote_url: "http://selenium:4444/"
  ]

I run mix via a wrapper script checks for Selenium being ready via the /status endpoint, so Selenium is definitely up and running by the time Wallaby is started. Am I setting the Selenium for Wallaby incorrectly? (I also had this setup working with Hound, which I was evaluating prior to trying Wallaby.)

docker-compose.yml

version: "3.3"
services:
  phoenix:
    build:
      context: .
      dockerfile: Dockerfile.dev
    ports:
      - 4000:4000
      - 4001:4001
      - 4002:4002
    depends_on:
      - db
      - selenium
    environment:
      - POSTGRES_HOST=db
    volumes:
      - type: bind
        source: .
        target: /paddy
      - type: volume
        source: dot-mix
        target: /home/paddy/.mix
      - type: volume
        source: dot-hex
        target: /home/paddy/.hex

  db:
    image: postgres:11
    environment:
      - POSTGRES_HOST_AUTH_METHOD=trust
    ports:
      - "${DB_PORT}:5432"
    volumes:
      - type: volume
        source: db
        target: /var/lib/postgresql/data

  selenium:
    image: selenium/standalone-firefox:4
    ports:
      - 4444:4444
      - 7900:7900
    volumes:
      - /dev/shm:/dev/shm

volumes:
  db:
  dot-mix:
  dot-hex:

The Selenium status check in the wrapper script for the phoenix image, as mentioned above.

echo 'Waiting for Selenium to be ready...'
while ! [ "$(curl -sSL http://selenium:4444/status | jq -r '.value.ready')" == "true" ]; do
  sleep 2
done

[mhanberg]

Please try setting your remote url to http://selenium:4444/wd/hub/

[aidalgol]

Oh, OK. Where should I be calling that function?

[mhanberg]

Since you are using Wallaby.Feature, you can pass options into the start_session function by setting them in the @session attribute above the feature.

defmodule MyFeatureTest do
  use ExUnit.Case
  use Wallaby.Feature

  @session [remote_url: "http://selenium:4444/wd/hub/"]
  feature "can login", %{session: session} do
    # test stuffs
  end
end

This is more of a short term solution until I add the ability to configure this with application config, as you will need to add that before every feature.

[aidalgol]

When I do that, I get

warning: module attribute @session was set but never used

and then the same error as before. I am running this on Elixir 1.10, if that makes a difference.

[aidalgol]

And then I read the documentation (which I should have done before posting just before) and realised that it should be @sessions (plural) and a list of keyword lists. So I have it working now! Thanks for your help!

[aidalgol]

This is more of a short term solution until I add the ability to configure this with application config, as you will need to add that before every feature.

@mhanberg Is there an open issue for this, or should I create one?