-
Notifications
You must be signed in to change notification settings - Fork 26
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
Beef up Kubernetes introspection on API tests #58
Labels
Comments
duanhongyi
added a commit
to duanhongyi/controller
that referenced
this issue
Nov 26, 2021
chore(controller): upgrade celery config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @helgi on September 15, 2016 19:7
Right now we generally just test that an AppSetting was created, updated and deleted... We are mostly exercising Django and DRF at that point, making sure some nuances are taken care of in the way we wrote a model or serializers.
The proposal here is to change tests to verify that Services are being updated, pods are created for autoscale, etc etc - Scheduler tests already takes care of a lot of that but more in-depth could be good
This is just taking AppSettings as an example and would apply to any model we have. Would prevent problems we saw with IP whitelisting, maintenance mode, routing and a few other things over the course of the project
Copied from original issue: deis/controller#1065
The text was updated successfully, but these errors were encountered: