Selenium Chrome - Features, integrations, alternatives & more
What it does
How it works
The Selenium Chrome service runs as a separate container but in the same network as the action to which is attached. This includes other services attached to the action. Buddy runs main action commands only once the service is fully initialized. There is no need to check Selenium Chrome availability on your own. The service is terminated once the action is completed. The service is cacheable it means data generated and stored by the service can be set persistent between action executions.
Selenium Chrome service features:
- Version setting including latest tag (the versions are pulled from Docker Hub)
- Hostname setting for connecting between action and other services
- The port is fixed (4444) and can’t be changed