Skip to content

Conversation

@stof
Copy link
Contributor

@stof stof commented Dec 4, 2025

The default value of TEST_MACHINE_BASE_PATH expects to find the mink/driver-testsuite in the vendor folder of the selenium2-driver package. As the CI installs both packages side by side, it needs to configure it explicitly.

Follow-up of #144 which was merged before I had a chance to look at failing tests.

The default value of `TEST_MACHINE_BASE_PATH` expects to find the `mink/driver-testsuite` in the vendor folder of the selenium2-driver package. As the CI installs both packages side by side, it needs to configure it explicitly.
@robocoder
Copy link
Member

@stof No worries. Thanks for the PRs.

@robocoder robocoder merged commit 184c8c4 into instaclick:master Dec 4, 2025
1 of 10 checks passed
@stof
Copy link
Contributor Author

stof commented Dec 4, 2025

this did not fix the failing tests. Something more might be missing.

@aik099
Copy link
Contributor

aik099 commented Dec 4, 2025

@stof , The ./vendor/mink/driver-testsuite/web-fixtures:/fixtures mapping is missing from the Docker configuration. This way Docker isn't seeing a file from a vendor folder of a test suite.

You can use the Docker compose-based version from the current build config: https://github.com/minkphp/MinkSelenium2Driver/blob/master/.github/workflows/tests.yml#L89C11-L89C109

@stof
Copy link
Contributor Author

stof commented Dec 4, 2025

@aik099 given that the mink/driver-testsuite is installed as a sibling of the driver in this CI setup (as both are installed as dependencies), I don't think we can use the docker compose setup of the driver repo.

@stof stof deleted the patch-1 branch December 4, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants