Use "docker-composer.yml" file during the build

[aik099]

Ported some changes from webdriver-classic-driver.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.85%. Comparing base (bedccba) to head (93152d9).
Report is 2 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master     #406      +/-   ##
============================================
+ Coverage     85.45%   85.85%   +0.39%     
  Complexity      182      182              
============================================
  Files             1        1              
  Lines           502      502              
============================================
+ Hits            429      431       +2     
+ Misses           73       71       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[aik099]

@uuf6429 , do you have an idea why this doesn't work?

When Selenium tries to load the http://host.docker.internal:8002/js_test.html page from the Docker container it gets the Unable to connect page back, which is generated either by Firefox or Selenium Server (see in log: https://github.com/minkphp/MinkSelenium2Driver/actions/runs/12723843225/job/35469480643?pr=406 ).

[uuf6429]

@aik099 my first guess would be something related to config, since the xml files are also a bit different:

• https://github.com/minkphp/MinkSelenium2Driver/blob/master/phpunit.xml.dist
• https://github.com/minkphp/webdriver-classic-driver/blob/main/phpunit.xml.dist

How I would troubleshoot it:

1. I would check the "PHP builtin server" (that mink launches) log - not sure if we store that somewhere..
2. since you set up the workflow for remote access, you can just docker exec -ti to get into the selenium container and ping that url you mentioned - if it works then probably it's some configuration problem

[aik099]

@aik099 my first guess would be something related to config, since the xml files are also a bit different:

• https://github.com/minkphp/MinkSelenium2Driver/blob/master/phpunit.xml.dist
• https://github.com/minkphp/webdriver-classic-driver/blob/main/phpunit.xml.dist

How I would troubleshoot it:

1. I would check the "PHP builtin server" (that mink launches) log - not sure if we store that somewhere..
2. since you set up the workflow for remote access, you can just docker exec -ti to get into the selenium container and ping that url you mentioned - if it works then probably it's some configuration problem

Thank you. The docker exec -ti d026a18ffd9d bash command revealed, that:

• Web Server was started on a localhost:8002
• docker container accessed Web Server via 172.17.0.1:8002

That fixed Selenium 2 image usage, however, the Selenium 3 images keep failing with a different error.

[aik099]

The Selenium 3 build is also fixed now.

Turned out, that the Selenium 3 container took a bit longer to start (then Selenium 2) and while ! nc -z localhost 4444 </dev/null; do echo Waiting for remote driver to start...; sleep 1; done command wasn't accounting for that (but I thought it should). The curl --retry 5 --retry-all-errors --retry-delay 1 --max-time 10 --head -X GET http://localhost:4444/wd/hub/status command, however, worked correctly. Mystery but it works now anyway.

@uuf6429 , Ready for review.

[uuf6429]

One small comment - looks good otherwise.