potiuk commented on issue #18127:
URL: https://github.com/apache/superset/issues/18127#issuecomment-1018468792


   > To protect against #17712 misconfig in pytest, there would be needed some 
kind of expected values list (which probably should be updated) - idk about 
actual implementation, probably will be more clear while planning this :) To be 
sure that any of those error won't occur some kind of dry-run would be needed. 
E.g. running helm on minikube will show the result and ability to successfully 
deploy the app. On cluster is quite easy though: 
https://helm.sh/docs/topics/chart_tests/
   
   Also another comment for that - in Airlfow we have > 350 unit tests, but we 
also have "kubernetes integration tests". Those are run also regularly in our 
CI and they consist of :
   
   * Building Production Image from latest sources
   * Extending the image to include test DAGs for Airflow
   * Deploying the image in few basic configuration to a kind 
(https://kind.sigs.k8s.io/docs/user/quick-start/)  cluster which is set-up 
during testing.
   * Running a small number of Pytest "integration" tests with the running 
application (very basic, literally "smoke" testing). 
   
   We also run separate "upgrade" tests. We update the chart and upgrade it 
after installing just to make sure that the upgrade scenario also works (we had 
some problems with hooks and migration jobs in the past). Those are really 
small number of tests but they give us confidence that we have not done 
something disastrous by accident.
   
   I can heartily recommend Kind for this kind of testing, it's also great for 
development environment when you would like to reproduce those kind of tests 
locally.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to