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
Currently we first spin up the kubernetes environment from make start command which first installs the helm chart on the kubernetes cluster and then run port-forwarding.
This is kinda of annoying when running tests, user has to do following
make start
# Wait time is long, anywhere from 5 mins to 20mins....# Run if helm timeouts, else `start` command will also perform port-forward
make port-forward
# After the above two are done, only then test can be run, test could be golang or npm
go test.# or
npm e2e:test
Proposal
Not sure how to fix this. Infra setup since takes time, should be setup once per testing batch. If setup per test, it would take too long.
Might want to comeup with better ways about this.
The text was updated successfully, but these errors were encountered:
Overview
Currently we first spin up the kubernetes environment from
make start
command which first installs the helm chart on the kubernetes cluster and then run port-forwarding.This is kinda of annoying when running tests, user has to do following
Proposal
Not sure how to fix this. Infra setup since takes time, should be setup once per testing batch. If setup per test, it would take too long.
Might want to comeup with better ways about this.
The text was updated successfully, but these errors were encountered: