* test: access specific field via "id". * test: access specific field via "id". * update snapshots. * Add test to validata description changes. * Change id def for input tag. * Skip unit tests * Add unit tests back and change id * Add a helper for clear default value in input field. Remove unnecessary 'tab' command * Add comment to explain the parameter name for tests Remove default value for runName before typing new value |
||
|---|---|---|
| .. | ||
| selenium-standalone-chrome-gcloud-nodejs.Docker | ||
| .dockerignore | ||
| Dockerfile | ||
| OWNERS | ||
| README.md | ||
| helloworld.spec.js | ||
| helloworld.yaml | ||
| package-lock.json | ||
| package.json | ||
| run_test.sh | ||
| tensorboard-example.spec.js | ||
| tensorboard-example.yaml | ||
| wdio.conf.js | ||
README.md
Frontend integration test
This test gets triggered by the end-to-end testing workflows.
Local run
-
Deploy KFP on a k8s cluster and enable port forwarding. Replace the default namespace
kubeflowbelow if needed.POD=`kubectl get pods -n kubeflow -l app=ml-pipeline-ui -o jsonpath='{.items[0].metadata.name}'` kubectl port-forward -n kubeflow ${POD} 3000:3000 & -
Build the container with the tests:
docker build . -t kfp-frontend-integration-test:local -
Run the test with enabled networking (this exposes your local networking stack to the testing container):
docker run --net=host kfp-frontend-integration-test:local --remote-run true -
Once completed, you can kill the background process of port-forwarding:
ps aux | grep '[k]ubectl port-forward' kill <PID>