- Introduction
- Docker Desktop
This directory contains the reference values for the Helm charts in the charts
directory. The reference values are used to test the Helm charts and ensure that they are working correctly. The reference values are stored in YAML files, which can be used to generate the expected output of the Helm charts.
Note: This guide is for macOS. For other operating systems, please refer to particular tool documentation.
brew install docker kubectl helm
Verify the installation
java -version
docker --version
kubectl version --client
helm version
Most users are able to installed Docker Desktop and start Kubernetes cluster in settings as below.
If you are having a local machine with good resources, configure Docker Desktop to use more resources. Then you can install orchestration containers with autoscaling capability.
Open a terminal, ensure kubectl
is able to connect to the cluster
kubectl cluster-info
Checkout file local-pvc-docker-desktop.yaml
kubectl apply -f local-pvc-docker-desktop.yaml
helm repo add docker-selenium https://www.selenium.dev/docker-selenium
helm repo update
Checkout file simplex-docker-desktop.yaml
helm upgrade -i selenium docker-selenium/selenium-grid \
--namespace default \
-f simplex-docker-desktop.yaml
- Grid components in cluster:
kubectl get pod -n default
- Grid UI: http://localhost/selenium
- Recordings manager: http://localhost/recordings
There is no Node visible on Grid UI. The browser nodes are created on demand when a test is started. The browser nodes are automatically removed when the test is finished.
Refer to get_started.py for a simple test using Python and Selenium. The test will run remotely on the Grid.
- Check the Grid UI to see the test running.
- Check the Recordings manager to see the video recording of the test.
- Check if the test passed or failed.