-
Notifications
You must be signed in to change notification settings - Fork 6
Iterations on the Developer Experience for writing specs #28
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
base: master
Are you sure you want to change the base?
Conversation
with builds-registry URLs
so let's look for alternative appoaches, starting with #26
Speed up dev loops that involve the assert runtime
need rbac can be created and deleted faster. Specs might not use the kubernetes client, or mighte have sufficient access with the default service account such as in ephemeral test clusters.
Make RBAC resources opt-in for the runtime-nodejs base
Next experiment after #26:
Unlike in dev environments where we aim for one-liners, during CI/CD it's trivial to maintain a set of environment variables for the container. The reason exit is so important is that with the current generation of kubernetes-assert we're having issues with specs that stay around for very long and thus produce lots of test data and other types of noise/costs. |
From the evaluation internally we've observed that:
|
Relatively low priority.
Relatively low priority. 10 s is a very good default.
Can we find criterias and runtime changes so that spec containers always exit?
The examples we run should dev both backend ans specs in the same If we succeed with the above, the y-assert hack in ystack could be replaced with something that basically does |
Timeout and delay should now be implemented for the cluster. Have not had enough time to see if it works properly. The logic should be there though. The image is not exited but there is a condition for where it should.
This reverts commit 66e447a.
Update jest.kubernetes-assertions-reporter.js
Feature branch goal: