Has anyone succeeded in creating a nerves firmware that contains a version of chrome/ium that wallaby can use?
Are you building a device that is going to test something else?
I would look at older attempts at nerves kiosks. I bet someone has done it with chrome.
Or is there a webkit driver for wallaby? Maybe it can drive cog?
Just speculating. In short, I haven’t 
Seems to be difficult. I am not going to test something, I need to scrape a website and present the information on a 7" display inside a hostel.
Wallaby seems to support chromedriver, selenium with either geckodriver (firefox) or chromedriver. Neither of which seems to be available for buildroot.
I am thinking now of doing the scraping in a container, I know Justin Schneck used to run docker on Nerves.
Chromedriver is just published as a binary you can download. Not for ARM64 though. But apparently the chromium chromedriver is often packaged for ARM64.
For containers I would reference the work Steffen has done with Balena Engine, an embedded-friendly adaptation of the Docker runtime: GitHub - nerves-containers/nerves_containers_rpi4
Yes, I’ve seen the chromedriver binary but as far as I can tell you still need chrome to be installed and the same version as that binary. I switched gears and decided to put the scraping part on a ubuntu based LXC container exposing an endpoint my nerves-based app can point to. But ofcourse the scraping that works fine on my dev Mac is not working in production. sigh.
At first my phoenix app wouldn’t boot because you need to include :ex_unit in :extra_applications or wallaby will crash, past that I see a lot of chrome processes being started but my code gets a timeout.
