Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improvements: Spinup infra within TestSetup #80

Open
Anmol1696 opened this issue Apr 22, 2023 · 0 comments
Open

improvements: Spinup infra within TestSetup #80

Anmol1696 opened this issue Apr 22, 2023 · 0 comments

Comments

@Anmol1696
Copy link
Collaborator

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant