We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Many of the scripts in test/e2e2 and hack/demo-env feel (and probably are) redundant, as they do the same things:
test/e2e2
hack/demo-env
That makes changes to one or the other cumbersome, and both scripts will slowly drift apart.
It would be great if we can use one single set of scripts for both scenarios, e2e tests and the demo env.
n/a
The text was updated successfully, but these errors were encountered:
I'll take a look at this.
Sorry, something went wrong.
jopit
Successfully merging a pull request may close this issue.
Is your task related to a problem? Please describe.
Many of the scripts in
test/e2e2
andhack/demo-env
feel (and probably are) redundant, as they do the same things:That makes changes to one or the other cumbersome, and both scripts will slowly drift apart.
Describe the solution you'd like
It would be great if we can use one single set of scripts for both scenarios, e2e tests and the demo env.
Describe alternatives you've considered
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: