Thanks for helping! I’m on Wallaby 0.26.2 and everything else matches, the only variation is the app name in config/test.exs (Chatter vs ChatterWeb):
config :chatter, ChatterWeb.Endpoint,
http: [port: 4002],
server: true
Changing that doesn’t resolve my issue FWIW.
EDIT: I had the wrong Chromedriver (I’d downloaded v87 but my Chrome is v86, so I replaced with v86). Now I get the following:
$ mix test
Compiling 18 files (.ex)
Generated chatter app
19:22:47.955 [error] GenServer Wallaby.Chrome.Chromedriver terminating
** (stop) :eacces
erlang.erl:2215: :erlang.open_port({:spawn_executable, 'c:/projects/chatter/_build/test/lib/wallaby/priv/run_command.sh'}, [:binary, :stream, :use_stdio, :stderr_to_stdout, :exit_status, {:args, ["chromedriver", "--log-level=OFF", "--port=57004"]}])
(wallaby 0.26.2) lib/wallaby/chrome/chromedriver/server.ex:96: Wallaby.Chrome.Chromedriver.Server.handle_continue/2
(stdlib 3.10) gen_server.erl:637: :gen_server.try_dispatch/4
(stdlib 3.10) gen_server.erl:388: :gen_server.loop/7
(stdlib 3.10) proc_lib.erl:249: :proc_lib.init_p_do_apply/3
Last message: {:continue, :start_chromedriver}
EDIT2: I am guessing it is a Windows permissions issue somehow but don’t know how to go about proving that.
thanks for a great book!
..
