You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2022/01/21 15:15:44 UTC

[GitHub] [superset] mik-laj edited a comment on issue #18127: Testing strategy of Helm Chart

mik-laj edited a comment on issue #18127:
URL: https://github.com/apache/superset/issues/18127#issuecomment-1018596225


   > We (in Superset) have already an ephemeral test environment on top of AWS ECS & AWS Fargate ( https://preset.io/blog/2021-4-28-ephemeral-test-environments-in-superset/ )
   
   I don't think we need to use external services as we can use KIND on Github Action. We have test environments running on Fargate because we want them to be available for longer than the duration of one build. 
   
   > Like Jarek pointed out, we will share our finding and optimization here as I think more projects can benefit from a pytest backed Helm unit-test framework.
   
   I agree. The Helm Chart testing framework written in Python is very convenient and has a low barrier to entry for projects that already use Python. For Golang project, terratest is also option.
   
   It is also worth mentioning the discussion we had at Airflow when we decided to migrate from tests written in YAML to the new Python framework:  https://github.com/apache/airflow/issues/11657
   


-- 
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-unsubscribe@superset.apache.org

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



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