fireproofsocks
Using wallaby: including chromedriver in release
I just stumbled across #wallaby – it’s a great library! I’m wondering if anyone has included chromedriver (or some other browser) in a mix release? Is it enough to ensure that the target machine has a viable version of chromedriver installed so when the release binary runs, a working version of chromedriver is available? Or would a different approach be preferred?
Marked As Solved
mhanberg
Wallaby is focused on being a testing library, and has some calls to ExUnit in it that will not be available in a release.
But, assuming you might fork and remove that (I think it’s one call to ExUnit.after_suite/1), you have two options.
The easiest is to just ensure that you have chrome and chromedriver installed on your host.
The latter would be to package them into your priv folder, make sure that gets copied into your release, and then configure Wallaby to look in those places for chromedriver and chrome.
Also Liked
Morzaram
For anyone looking for a way to use current wallaby in production and hitting ExUnit.after_suite/1
What worked for me is to include :ex_unit in your extra_applications
def application do
[
mod: {MyCool.Application, []},
extra_applications: [:logger, :runtime_tools, :ex_unit]
]
end
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"