You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To debug or write feature specs, it is absolutely necessary to execute them in a non-headless browser. Generally, to do this, the HEADLESS=false environment variable can be set. With the current container setup it is not possible to execute the features specs in this mode – a solution has to be engineered and documented.
Work around:
Start database/rails server with Docker Compose.
On the local machine (not within a container!), from the core directory app/hitobito, use the following command to execute one or more feature specs in non-headless mode (Ruby/Bundler must be available, Gems installed):
I have previously had success with sharing the X socket with a container, such that the container can open windows on the host. On Linux and Mac OS, this can be done as follows:
If you are on Mac, install the XQuartz X11 server (brew cask install xquartz) and restart your machine
Run xhost local:root in order to allow the root user from the Docker container to send messages to the X server
Configure the service that should open the windows as follows in docker-compose.yml:
I added the DISPLAY var and the volume from @carlobeltrame post.
chromium now starts, but the opened window is just blank and I can't see any content.
also the specs are failing when running with HEADLESS=false
To debug or write feature specs, it is absolutely necessary to execute them in a non-headless browser. Generally, to do this, the
HEADLESS=false
environment variable can be set. With the current container setup it is not possible to execute the features specs in this mode – a solution has to be engineered and documented.Work around:
app/hitobito
, use the following command to execute one or more feature specs in non-headless mode (Ruby/Bundler must be available, Gems installed):See also #7
The text was updated successfully, but these errors were encountered: