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
I am not able to run the codeception locally as I am using a clean docker compose setup (locally security approved) and the bootstrap.php file for the tests tries to run docker compose commands by starting processes (but I am already in a PHP container) and also tries to start node in the same container (one container on process/job).
It seams to me that codeception (or the way it is used in this project) is not docker only development environment friendly. In its current setup it is not possible to run the test without have everything installed locally (which for us is not possible).
In actions the tests fails with The command "'npx' 'selenium-standalone' 'install'" failed. see #2326
Are there any thoughts about using an clean php-unit to do unit test? If I look at https://codeception.com/docs/AcceptanceTests is seams that selenium is not a requirement and everything test related could stay in PHP land.
The text was updated successfully, but these errors were encountered:
I am not able to run the codeception locally as I am using a clean docker compose setup (locally security approved) and the bootstrap.php file for the tests tries to run docker compose commands by starting processes (but I am already in a PHP container) and also tries to start node in the same container (one container on process/job).
It seams to me that codeception (or the way it is used in this project) is not docker only development environment friendly. In its current setup it is not possible to run the test without have everything installed locally (which for us is not possible).
In actions the tests fails with
The command "'npx' 'selenium-standalone' 'install'" failed.
see #2326Are there any thoughts about using an clean php-unit to do unit test? If I look at https://codeception.com/docs/AcceptanceTests is seams that selenium is not a requirement and everything test related could stay in PHP land.
The text was updated successfully, but these errors were encountered: